PagerDuty
Create PagerDuty incidents from vendor alerts. Your team manages acknowledgement in PagerDuty.
This alert channel is included in Pro and Enterprise. Compare plans.
Setup
- 1
Add an Events API v2 integration
In PagerDuty: Service → Integrations → Add an integration → Events API v2. Copy the integration key (also called the routing key).
- 2
Open Settings → Alerts
Click Add channel → PagerDuty and paste the routing key.
- 3
Map severity
By default
degraded→warning,partial_outage→error,major_outage→critical. Use your PagerDuty workflow to route the resulting severity. - 4
Test delivery
Send a test from CheckUpstream and confirm that it reaches the intended PagerDuty service. Review the closure conditions below before relying on the integration.
When alerts close
CheckUpstream requests closure only after the vendor marks its incident resolved, while the alert is active and unmuted and the channel is enabled with its original routing key.
A missing feed entry, tracking timeout or unknown closure reason leaves the alert open. A changed key does not redirect older alerts; manage them in the original service. Vendor resolution does not confirm your app has recovered. See alert delivery and closure.
Configure the integration
Add the destination or credentials, then verify the connection.