Alerts and Notifications
This page is also in the Groundskeeper wiki: https://github.com/rsjsoftwareltd/groundskeeper/wiki/Alerts-and-Notifications
Groundskeeper tells you about problems three ways: a weekly digest email, immediate alert emails, and messages to a Teams or Slack channel. All three are set up under General Settings -> Notifications.
Email needs the Email & SMTP card filled in first: switch on Enable email notifications, enter your mail server, a From address and at least one recipient, then click Test SMTP. Until that is done, neither the digest nor the immediate alerts are sent.
The events these messages are about are the ones on the Dashboard feed, where you can also acknowledge and snooze them. The Alerts Page lists the warnings and criticals still to deal with, and has buttons to send the digest and to test email and Teams.
The weekly digest #
An email on a schedule you choose (Monday 07:00 by default) summarising the week. Goes to the recipients in the Email & SMTP card. Tick Send digest even if everything is healthy if you want the reassurance of a quiet week in writing. Send digest now sends one straight away.
Immediate alerts #
The moment a warning or critical event lands on the feed, an email can go out. The Immediate alert routing card controls this:
- Alert recipients -- who gets the immediate emails. Leave blank and they go to the digest recipients.
- Email on critical / warning events -- criticals are on by default, warnings off. Warnings are more frequent; turn them on once the estate is quiet.
- Quiet hours -- alerts raised between these times are held back and not sent later. The feed still records them. 22:00 to 07:00 is a common choice, and a window that crosses midnight works as you would expect.
- Mute these connectors -- no alert emails for a connector's events. They stay on the feed and the dashboard; only the emails stop. Useful for a connector that is noisy while you tune it.
Planned downtime is a different thing: see Maintenance Windows for telling Groundskeeper a device is expected to be off. An outage inside a window is recorded on the feed as information, not as a warning or critical, so no alert goes out for it at all -- rather than the email being held back.
Teams and Slack #
The Teams & Slack Webhook card posts alerts to a chat channel. For Teams, in the channel choose Workflows, then Post to a channel when a webhook request is received, and paste the address it gives you. For Slack, use an incoming webhook address. Switch on Enable webhook alerts, choose whether to send on critical events (on by default) and on warning events (off by default), save, and click Send test message.
The Immediate alert routing card has its own quiet hours and muting for the webhook, separate from email, so you can keep a chat channel live overnight while emails pause.
Where it is stored #
Under notifications.email and notifications.webhook in config.yaml, so a settings backup carries it.
Last updated: 2026-10-18 (v0.192.7)