Alerts and Notifications

Alerts and Notifications

Groundskeeper tells you about problems three ways. All three are set up under Settings -> Notifications.

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.

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.

The same quiet hours and muting are available for the Teams & Slack webhook, separately, so you can keep a chat channel live overnight while emails pause.

Planned downtime is a different thing: see Maintenance Windows for telling Groundskeeper a device is expected to be off, which stops the alert being raised at all rather than holding the email back.

Where it is stored

Under notifications.email and notifications.webhook in config.yaml, so a settings backup carries it.

Last updated: 2026-09-03 (v0.126.0)