Incidents
Incidents represent periods where a monitor is unhealthy.
Lifecycle
Down Transition
When monitor status changes to down:
consecutive_failuresincrements- an active incident is created if none exists
- subscribers and alert channels are notified
Still Down
If checks keep failing while already down:
- the active incident remains open
- no new incident is created
- no duplicate down alert is sent by default flow
Recovery Transition
When status changes back to up:
- active incident is marked resolved
consecutive_failuresresets to0- recovery notifications can be sent
Incident Cause
Cause is derived from latest check details, for example:
- network/timeout/SSL errors
- assertion failures
- HTTP 4xx/5xx outcomes