Skip to main content
Connect DevHelm to PagerDuty to automatically trigger and resolve incidents. DevHelm uses the PagerDuty Events API v2, maintaining incident state — when a DevHelm incident resolves, the corresponding PagerDuty alert resolves too. Plan requirement: Pro or above

​
Setup

1

Get your PagerDuty routing key

  1. In PagerDuty, go to Services → select your service → Integrations
  2. Click Add Integration and select Events API v2
  3. Copy the Integration Key (this is your routing key)
2

Create the alert channel in DevHelm

devhelm alert-channels create \
  --name "On-Call PagerDuty" \
  --type PAGERDUTY \
  --routing-key "your-events-api-v2-routing-key"
3

Test the channel

devhelm alert-channels test <channel-id>

​
Configuration

FieldDescriptionRequired
routingKeyPagerDuty Events API v2 routing (integration) keyYes
severityOverrideOverride PagerDuty severity: critical, error, warning, infoNo

​
Lifecycle behavior

PagerDuty uses trigger-resolve lifecycle:
DevHelm eventPagerDuty action
Incident createdTriggers a new alert
Incident resolvedResolves the corresponding alert
Incident reopenedTriggers a new alert
This keeps PagerDuty incident state in sync with DevHelm — no manual cleanup needed.

​
Severity mapping

By default, DevHelm maps severities to PagerDuty:
DevHelm severityPagerDuty severity
DOWNcritical
DEGRADEDwarning
Use severityOverride to force all alerts to a specific PagerDuty severity regardless of the DevHelm incident severity.

​
Troubleshooting

  1. Verify the routing key is for Events API v2 (not the REST API)
  2. Check that the PagerDuty service is enabled and has an escalation policy
  3. Run devhelm alert-channels test <id> to verify delivery
Resolution uses the same routing key. If you rotated the key in PagerDuty, update it in DevHelm too.