Notification Behavior
The exact specification of when, where, and how many times notifications are sent. For per-channel setup, see the notification guides.
Notification Events
Section titled “Notification Events”| Event | Timing | Severity |
|---|---|---|
| Incident created | When an incident is confirmed after 5 consecutive down checks | critical |
| Warning incident created | When a monitor becomes degraded | warning |
| Incident resolved | On automatic resolution after recovery | – |
| Web change detected | When a Web Change monitor detects a difference | – |
| Maintenance started / ended | At the start and end of a maintenance window | – |
Channel Resolution
Section titled “Channel Resolution”- If a monitor has at least one channel attached directly, notifications go only to the active, verified channels among them (team-wide channels are not used)
- If the monitor has no direct channels, notifications go to the team-wide active, verified channels
- If no eligible channel exists, nothing is sent
Flap Suppression
Section titled “Flap Suppression”When a monitor rapidly alternates between down and up (flapping), suppression prevents a notification flood.
- If a monitor generates more than 3 notification events within the last 10 minutes, subsequent notifications are suppressed
- The counter automatically expires after 10 minutes
- Incidents are still recorded while suppressed (visible in the dashboard)
- Maintenance start/end notifications are exempt from flap suppression
Duplicate Prevention
Section titled “Duplicate Prevention”The same combination of incident, channel, and event type is sent at most once. Even if the delivery infrastructure retries, you will not receive the same notification twice.
Partial Channel Failures
Section titled “Partial Channel Failures”If some channels fail while sending to multiple channels, the remaining channels are still attempted. Delivery counts as complete if at least one channel succeeds; it is retried only when every channel fails.
Webhook Subscriptions
Section titled “Webhook Subscriptions”Separate from notification channels, webhook subscriptions deliver events over HTTP.
- Events:
incident.created/incident.resolved/webchange.detected(only subscribed events are delivered) - Delivery is attempted up to 3 times — the initial send plus up to 2 retries (best-effort delivery)