Subscriber notification events
Which incident and maintenance transitions trigger subscriber emails.
When an incident or maintenance fires, Observer notifies confirmed subscribers on the affected page. The dispatch matrix below lists which event types trigger subscriber email and which do not.
Trigger matrix
| Event | Triggers subscriber email |
|---|---|
incident.created | No (draft state). |
incident.published | Yes. |
incident.updated | No (avoids notification spam on minor edits). |
incident.message_added | Yes. |
incident.resolved | Yes. |
incident.deleted | No. |
maintenance.scheduled | Yes. |
maintenance.starting_soon | Yes (1h pre-warn). |
maintenance.started | No (the starting-soon mail covered it). |
maintenance.completed | Yes. |
maintenance.canceled | Yes. |
Filter scopes
When a subscriber has chosen specific services or metrics, the dispatch only fires when at least one of the incident's affected services or metrics intersects that selection. Subscribers who chose no filters receive every relevant event for the page.
Customer-scoped incidents
Customer-scoped incidents reach only subscribers tied to the listed customers. Outbound webhook subscribers are unaffected: they always receive every event their subscription opted into, regardless of customer scoping.
Per-attempt audit
The console Subscribers view shows the most recent delivery outcome per subscriber (delivered, error, or skipped) for triage.