Skip to main content
When an incident or maintenance window changes, Observer notifies the confirmed subscribers of every page it appears on. The same rules apply to every subscriber channel: email, Slack, Microsoft Teams, and webhook. The matrix below lists which event types notify subscribers.

​
Trigger matrix

Webhook subscribers receive these as JSON; see the subscriber webhook reference for the payloads.

​
Filter scopes

When a subscriber has chosen specific services or metrics, an update reaches them when at least one of its affected services, or a metric behind one of those services, is among their selection, or when the update names no affected services (a page-wide update). Subscribers who chose no filters receive every relevant event for the page. Recoveries always deliver: incident.resolved, maintenance.completed, and maintenance.canceled reach every subscriber who was notified earlier about the same incident or maintenance, even if its affected services changed in between.

​
Customer-scoped incidents

Customer-scoped incidents reach only subscribers tied to the listed customers. Alerts destinations are not filtered by customer scope: a destination receives the incident when it is org-wide or scoped to one of the incident’s pages.

​
Per-attempt audit

Every send is recorded per subscriber and event, so an event is not sent twice to the same subscriber. The console Subscribers view lists each subscriber’s subscription status (confirmed, unconfirmed, or unsubscribed), not individual delivery outcomes.