PagerDuty Integration for Server & Uptime Monitoring
When a monitor or server goes down, Statance triggers a PagerDuty incident with a deduplication key per Statance incident, and resolves the same incident when it recovers — so your on-call rotation and escalation policies apply. Test messages and security (CVE) alerts trigger an incident without auto-resolving.
Set up PagerDuty
Add an integration to a service
In PagerDuty, open a service → Integrations → Add “Events API V2” and copy the integration (routing) key.
Add it to a recipient
Paste the routing key into the PagerDuty field.
API: set config.pagerdutyKey on a recipient — see notification docs.
What you’ll receive
- Down alert with the monitor or server name, cause and start time
- Recovery alert with total downtime
- Link straight to the incident and its AI summary
FAQ
Do incidents auto-resolve?
Monitor and server incidents do — the recovery event resolves the matching PagerDuty incident. Test messages and security/CVE alerts trigger without auto-resolve, so close those in PagerDuty yourself.