Alerts Page

This page is also in the Groundskeeper wiki: https://github.com/rsjsoftwareltd/groundskeeper/wiki/Alerts-Page

The Alerts page is the short list of things that need someone to look at them right now: every warning and critical event that nobody has dealt with yet. It also holds the buttons for the weekly digest and the settings for the Teams bot.

Open it from the Alerts item in the sidebar, or at https://<server-address>:8443/alerts. Admin and technician accounts can open it. An SLT account cannot.

This page is about the screen. For how alert emails and chat messages are set up, see Alerts and Notifications.

Active alerts #

This is the main list, at the bottom of the page. The line under the page title sums it up, for example "1 critical, 2 warnings need attention". A round badge next to the list heading shows the total. It is red if any of them is critical, and amber if they are all warnings.

An event is on this list when all of these are true:

It is a warning or a critical. Information and OK events are not listed here. They are on the Dashboard feed.
Nobody has acknowledged it or snoozed it.
It has not been replaced by a newer event for the same condition. A problem that has since recovered drops off the list by itself.

The list is built from the 200 most recent events, plus every problem that is still open however old. A problem that was reported once and has been quiet since, such as a service that went down weeks ago, therefore stays on the list until it is fixed, acknowledged or snoozed.

The page checks again every minute.

Each row shows the title and detail, the connector that raised it, and how long ago. Its buttons are:

Acknowledge -- takes it off the list. There is no timer. It stays on the Dashboard feed, dimmed, where you can unacknowledge it.
Snooze -- takes it off the list for 15 minutes, 1 hour, 4 hours or until tomorrow (8am). When the time is up it comes back.
Log what you did -- opens the Incident Log with a new entry ready to fill in. The entry is linked to this alert, and its title starts "Dealt with:" followed by the alert's title.
View in feed -- opens the Dashboard.

Acknowledge and snooze work the same way as on the Dashboard. If one of them fails, a red message above the list says so and the alert stays on the list.

When the list is empty #

An empty list is not always good news, and the page says which it is:

No active alerts -- all clear. The list loaded in full, and every warning and critical event is dealt with.
Nothing in the most recent events needs attention. Shown in amber, with a note that this is not an all-clear. The recent events were fine but the older open problems could not be loaded just now. The page tries again every minute.
Could not load alerts. The page could not reach the feed at all.

Weekly email digest #

The top-left card is headed "Weekly email digest -- preview". It is a fixed example of how the email is laid out. The figures, names and dates in it (a low-disk warning on SERVER01, "Week ending Friday 6 June 2026") are made up for illustration. They are not your own data. Your real digest is built when it is sent.

The card links to General Settings -> Notifications, where you choose the day, time and recipients.

Digest actions #

Three buttons sit to the right of the preview. The result of each appears below the buttons, starting "OK:" or "Error:", with the message from the server.

Send digest now -- sends the weekly digest straight away, to the recipients set up under Notifications.
Test email settings -- checks that Groundskeeper can connect to your mail server with the settings saved under Notifications. It does not send the digest.
Send a test message to Teams or Slack -- sends a test message to the webhook saved under Notifications.

All three use the settings already saved. If email is not set up yet, start with General Settings -> Notifications.

Teams bot -- Ask Groundskeeper #

This card lets people ask Groundskeeper a question from Microsoft Teams or Copilot Studio. It is separate from the Teams and Slack alert messages.

Turn on the Teams bot -- the bot is off until this is ticked.
Shared secret -- a password that Teams or Copilot sends with each question, so Groundskeeper knows the request is genuine. Generate makes a long random one and shows it. Show and Hide reveal or hide what you have typed. Copy a generated secret into your bot or Copilot Studio settings before you click Save: once it is saved it is stored encrypted and cannot be shown again. If one is already set, the hint under the box says so. Leave the box blank to keep it, or type a new value to replace it.
Save bot settings -- saves the tick box and, if you typed one, the secret.
Test AI response -- asks the AI "What is the current IT status?" and shows the answer. It checks that the AI works. It does not use the secret, so it does not prove that Teams can reach the bot.

Things to know:

The bot refuses every question until it is both switched on and has a secret. There is no open mode.
It also needs AI switched on under General Settings -> AI Provider. Without it, the bot answers that the AI is not enabled. See AI Features.
Teams or Copilot Studio sends questions to POST /api/bot/teams/message, with the secret in a header called X-Groundskeeper-Token. That address works without a Groundskeeper sign-in, which is why the secret is required.
Each bot question counts towards the daily AI limit. If the limit is reached, the bot's answer says so.

Who can do what #

The list of active alerts and its Acknowledge, Snooze and Log what you did buttons work for admin and technician accounts alike.

The digest buttons and the Teams bot card change or test settings. They are available to admin accounts only. A technician who clicks them gets an error, not the result.