Docs/Notifications
Notifications
Alerts route to channels you configure under Settings → Integrations. All channels are team-wide today — every enabled destination receives every event.
Channels
| Channel | Destinations | Plan | Status |
|---|---|---|---|
| All team members | All plans | Available | |
| Slack | Multiple workspaces / channels | Pro | Available |
| Telegram | Multiple chats, groups, topics | Pro | Available |
| Webhook | — | — | Coming soon |
| — | — | Coming soon |
Events
A notification is sent for each of these:
incident.started— a monitor or cron transitioned to downincident.resolved— it transitioned back to upcron.missed— a scheduled cron didn't ping in timecron.recovered— a missed cron pinged againlighthouse.offline/lighthouse.recovered— agent connectivitylighthouse.started/lighthouse.stopped— agent lifecycle
Slack and Telegram destinations have toggles for notify on incident start and notify on incident resolve, so you can opt out of recovery messages if you only want pages.
Email is enabled for every team member by default. There's nothing
to configure — alerts are delivered to the address you signed up
with. The from-address is [email protected].
Routing
There's no per-monitor routing override yet. Every enabled destination receives every event. If you need different routing per team or project, create separate teams (the same user can be a member of multiple).
Retries
Failed notification deliveries are retried up to three times with backoff. After that the failure is logged on the destination and you can re-send manually.