Skip to main content
Observer integrates with PagerDuty through the Events API V2. One Observer incident maps to one PagerDuty incident across its whole lifecycle. Agent, metric, and SLO alerts also open and resolve their own on-call incident.

​
Set up

1

Create an Events API V2 integration

In PagerDuty, open the service that should receive alerts, go to Integrations, and add an Events API V2 integration. Copy the Integration Key (also called the routing key).
2

Add the integration in Observer

In the console, open Alerts, choose Add alert, pick PagerDuty, and paste it into Integration (routing) key. Choose org-wide or a single page, then save.
3

Test it

Use Send test from the row’s actions menu. A test trigger should open an incident on the PagerDuty service. Resolve it in PagerDuty when you are done.

​
Lifecycle mapping

Every action carries a dedup key derived from the Observer incident id (observer-incident-<id>). PagerDuty uses that key to attach updates to the existing incident and to resolve the right one, so a published, updated, and resolved sequence produces one PagerDuty incident, not three.
Severity mappingObserver severities map to PagerDuty severities: critical to critical, major to error, minor to warning. Scheduled maintenance does not page.

​
Troubleshooting

  • No incident appears: confirm the Integration Key is from an Events API V2 integration (not a different integration type), and that the integration is enabled in Observer.
  • A bad key: PagerDuty returns a 4xx, which Observer treats as a configuration error and does not retry. Fix the key and test again.