PagerDuty

Page on-call through PagerDuty

Already run on-call in PagerDuty? Pingstack sends each incident to a PagerDuty service, and your schedules, escalation policies and urgency rules decide who gets paged.

How it works

• One PagerDuty incident per outage. When a check goes down, late or degraded, Pingstack triggers an alert. If the check’s status changes, Pingstack updates that same PagerDuty incident and doesn’t open a new one. When the check recovers, the incident resolves on its own.
• You choose the severity. Pick the severity for down, late and degraded checks on each channel. By default, down is critical, late is error and degraded is warning.
• Context comes with it. Each alert carries the check name, what failed, when it started and a link back to the check.
• Test before you rely on it. Send a test alert from the channel page. Pingstack opens it and resolves it straight away.

Set it up

1. In PagerDuty, add an Events API V2 integration to the service you want paged and copy its integration key.
2. In Pingstack, add a PagerDuty channel to a notification group, paste the key and choose severities.
3. Add the group to checks. Incidents and recoveries go to PagerDuty.

Want a phone call without PagerDuty? Pingstack can call the person on duty directly.