Integrations

PagerDuty Integration

Trigger PagerDuty incidents when a monitor goes down and automatically resolve them when it recovers. Uses PagerDuty Events API v2 with deduplication so you won't get duplicate pages. Pro plan required.

Setup

  1. In PagerDuty, go to Services → Service Directory
  2. Select the service you want DeadPing to alert, or click + New Service to create one
  3. Go to the Integrations tab and click + Add an Integration
  4. Search for “Events API v2” and add it
  5. Click the integration name to view its details and copy the Integration Key (routing key) — it looks like a1b2c3d4e5f6789012345678abcdef01
  6. In DeadPing, go to Settings → Integrations, expand PagerDuty, paste the routing key, and click Save

Trigger and Resolve Behavior

DeadPing uses PagerDuty's deduplication key (dedup_key) to tie trigger and resolve events together for the same monitor:

  • When a monitor goes DOWN: DeadPing sends a trigger event with dedup_key set to the monitor ID (e.g. deadping-monitor-abc123)
  • When the monitor RECOVERS: DeadPing sends a resolve event with the same dedup_key
  • PagerDuty deduplicates using the key — if multiple down alerts fire before a recovery, only one incident is created and it resolves cleanly when the monitor comes back up

Payload Format

Events are sent to the PagerDuty Events API v2 endpoint using your routing key:

Trigger event (monitor down)
POST https://events.pagerduty.com/v2/enqueue

{
  "routing_key": "your-routing-key",
  "event_action": "trigger",
  "dedup_key": "deadping-monitor-abc123",
  "payload": {
    "summary": "Monitor \"nightly-backup\" is DOWN — expected every 60m",
    "severity": "critical",
    "source": "DeadPing",
    "custom_details": {
      "monitor": "nightly-backup",
      "expected_interval": "60 minutes",
      "last_ping": "Mon, 09 Mar 2026 03:00:12 UTC",
      "grace_period": "300s",
      "dashboard_url": "https://deadping.io/dashboard/abc123"
    }
  },
  "links": [
    { "href": "https://deadping.io/dashboard/abc123", "text": "View in DeadPing" }
  ]
}
Resolve event (monitor recovered)
POST https://events.pagerduty.com/v2/enqueue

{
  "routing_key": "your-routing-key",
  "event_action": "resolve",
  "dedup_key": "deadping-monitor-abc123",
  "payload": {
    "summary": "Monitor \"nightly-backup\" has recovered",
    "severity": "info",
    "source": "DeadPing",
    "custom_details": {
      "monitor": "nightly-backup",
      "downtime": "~14 minutes"
    }
  }
}

Anomaly Alerts

Anomaly alerts (Pro+) also trigger PagerDuty events. These use severity: "warning" and event_action: "trigger" with a separate dedup_key scoped to the anomaly: deadping-anomaly-{anomalyId}. This keeps anomaly incidents distinct from down/recovery incidents so they can be acknowledged and resolved independently.

Anomaly types that trigger PagerDuty alerts: duration spikes, irregular ping frequency, and error rate surges. All three use severity: "warning" rather than "critical" to distinguish them from a full outage.

Plan Requirement

PagerDuty integration requires the Pro plan. Configure your routing key at Settings → Integrations.