PagerDuty: no connection yet; route monitor alerts another way
There is no PagerDuty connection for customers today: no Events API v2 payload, no routing-key field and no incident per run. Synthetic-monitor alerts can still reach on-call through an Opsgenie sink, or through a generic webhook sink pointed at a relay of your own.
Which way the data flows
Nothing goes to PagerDuty from Dokimore today.
Set it up
- If your on-call already runs in Opsgenie, add an Opsgenie alert sink instead.
- Otherwise add a generic webhook sink that points at a small relay you run, such as a serverless function.
- In the relay, map the alert JSON to an Events API v2 trigger with your routing key and forward it to PagerDuty.
Where it stops
Stated plainly
- Only synthetic-monitor alerts leave Dokimore; failed test runs and SLO breaches do not.
- The generic webhook body is unsigned JSON, so protect the relay URL like a secret.
Questions buyers ask
Will a PagerDuty connection be added?
It is not built for customers today. If it ships, this page will name the file that implements it, as every page in this directory does.
Why is it not listed as supported?
Because a payload template that nothing sends is not an integration, and an on-call team that relied on it would never be paged.
Where it is implemented
The files in our code that carry this integration. A catalogue test checks that each still exists, so this page cannot outlive the feature.
backend/src/modules/developer-experience/services/alert-sink-dispatcher.ts
Related pages
Also under Alerting and chat: Slack · Microsoft Teams · Opsgenie · Webhooks
Try it against your own pipeline
Free plan, no card; the integrations on this page are on every plan.