PagerDuty integration: routing keys and severity mapping
PagerDuty integration
PagerDuty (PD) is the second-most-used channel in DevFlow.
install
In PagerDuty, create a service of type Events API v2 and copy the Integration Key (sometimes called "routing key").
In DevFlow:
devflow channels add payments-oncall --type pagerduty --routing-key R012345ABCDEFOr in the dashboard. The integration key never leaves DevFlow — it's stored as a variables-and-secrets under the hood.
severity mapping
DevFlow severities map to PD severities:
| DevFlow severity | PagerDuty severity |
|---|---|
| critical | critical |
| error | error |
| warning | warning |
| info | info |
Severity comes from the alert rule. SLO fast-burn is critical by default (slo-multi-window-alerting); slow-burn is warning.
dedup key
We send PD a dedup key of devflow:incident:<incident-id>. PD uses that to deduplicate noisy retries on its end as well as ours.
acknowledgement bidirectional
When the on-call ack's in PagerDuty, DevFlow gets the webhook back and the incident is marked acknowledged in our UI. Vice versa works too — /devflow ack from Slack (slack-integration) propagates to PagerDuty.
resolve
Auto-resolve in DevFlow (incident-management) sends a PD resolve event. PD-side manual resolves come back via webhook to close DevFlow's incident.
removing
PagerDuty admins can remove the integration at any time. The next failed delivery surfaces a banner in DevFlow pointing to the reinstall flow.