PagerDuty
Route incidents to PagerDuty with full lifecycle — firing opens an incident, recovery auto-resolves it.
WatchFor integrates with PagerDuty Events API v2. A firing alert opens a PagerDuty incident; when the underlying problem clears, WatchFor resolves the same incident automatically — so on-call isn't left paging over something that's already fixed.
Setup
Create (or open) a PagerDuty service
In PagerDuty, go to Services → Service Directory and add or open the service that should receive WatchFor alerts.
Add an Events API V2 integration
On the service's Integrations tab, add an integration of type Events API V2. PagerDuty generates a 32-character Integration Key.
Add the channel in WatchFor
Go to Alerting → Channels → Add channel → PagerDuty, paste the Integration Key as the Routing Key, and pick your Service Region (leave as US / Global unless your PagerDuty account is in the EU region).
Send a test
Press Send test — a triggered incident should appear in PagerDuty within a few seconds.
Routing keys are region-specific. If your PagerDuty account is in the EU service region, choose EU — a US key sent to the EU endpoint (or vice versa) is rejected.
What PagerDuty receives
- Severity mapped from the alert (critical / warning / info).
- Deduplication — every firing/recovery for the same alert rule shares a stable dedup key, so re-fires update one incident instead of spawning many, and the recovery closes exactly that incident.
- Rich custom details — monitor, diagnosis, expected vs detected values, confirming locations, rule version — visible on the PagerDuty incident.
- A "View in WatchFor" link on the incident header, straight to the incident page.
Severity & escalation tips
Map WatchFor rule severities to PagerDuty urgencies via your service's settings: send Critical WatchFor alerts to a high-urgency escalation policy and Warning to low-urgency, so a warning doesn't wake anyone at 3 AM. Configure this on the PagerDuty side (service → urgency rules).
Troubleshooting
- Test fails / nothing in PagerDuty — double-check the Routing Key is an Events API V2 integration key (not an older Events API v1 key or a REST API token), and that the Service Region matches your account.
- Incident opens but never resolves — this shouldn't happen (dedup keys are stable); if it does, confirm the same channel handled both the firing and the recovery routing.