Setup
1
Get your PagerDuty routing key
- In PagerDuty, go to Services → select your service → Integrations
- Click Add Integration and select Events API v2
- Copy the Integration Key (this is your routing key)
2
Create the alert channel in DevHelm
3
Test the channel
Configuration
Lifecycle behavior
PagerDuty uses trigger-resolve lifecycle:
This keeps PagerDuty incident state in sync with DevHelm — no manual cleanup needed.
Severity mapping
By default, DevHelm maps severities to PagerDuty:
Use
severityOverride to force all alerts to a specific PagerDuty severity regardless of the DevHelm incident severity.
Troubleshooting
Alerts not triggering
Alerts not triggering
- Verify the routing key is for Events API v2 (not the REST API)
- Check that the PagerDuty service is enabled and has an escalation policy
- Run
devhelm alert-channels test <id>to verify delivery
Alerts not auto-resolving
Alerts not auto-resolving
Resolution uses the same routing key. If you rotated the key in PagerDuty, update it in DevHelm too.