Skip to content
downpipes docs

Send downpipes alerts to PagerDuty

PagerDuty receives downpipes alerts through its Events API v2. The engine posts each event to PagerDuty’s enqueue endpoint with your routing key. A failing or stale downpipe triggers an incident, and when the same downpipe recovers, downpipes sends a resolve for the incident it opened, so on-call sees it clear on its own.

Because the engine makes the outbound call, a Cloudflare Access perimeter on your console never blocks delivery: there is no inbound request for Access to turn away.

What you need

  • A PagerDuty service you can edit, with permission to add an Events API v2 integration to it.
  • Access to the downpipes console with the notify-config capability (Operator, Approver or Owner) to add and test the channel.

Set it up

  1. In PagerDuty, open the service you want alerts on, go to its Integrations tab, and add an Events API v2 integration.
  2. Copy the Integration Key the integration shows. PagerDuty also calls this the routing key.
  3. In the downpipes console, open Notifications, choose Add a channel and pick PagerDuty (Events API v2). Adding a channel needs the notify-config capability, so an Operator, Approver or Owner can add one.
  4. Paste the Integration Key into the PagerDuty routing key field, give the channel a name you recognise, and save it. A rule then routes events to it.
  5. Choose Test on the channel row. downpipes sends one redaction-safe test so you can confirm delivery without sending real alert content, then check the incident arrived in PagerDuty. The test opens a real info-severity incident that downpipes does not resolve, so close it in PagerDuty when you are done; a repeated test collapses onto the same incident through the dedup key rather than opening a new one.

Good to know

  • One setting, your routing key. PagerDuty is the only channel with a single credential and a fixed endpoint. downpipes posts to PagerDuty’s own enqueue URL, so there is no URL for you to supply and nothing internal for an egress screen to catch.
  • Dedup and auto-resolve are built in. downpipes sends a stable dedup key derived from the downpipe and the event, so repeated firings collapse onto one incident and a recovery resolves that same incident rather than opening a new one. The alert body carries a short summary, the severity and a source label, never a backup’s contents or any secret.

Last updated .