What it is
Events API v2. Every alert opens an incident on the service behind the integration key; the alert id is the dedup key.
Set up
About 5 minutes to a working channel.
- 01Add an Events API v2 integration to the service. PagerDuty → Services → the service → Integrations → Add integration → “Events API V2”. Copy the Integration Key (32 hex characters).
- 02Paste the key, then Test. Test enqueues a low-severity event and resolves it right away, so nobody is paged. If the key is wrong, PagerDuty answers 400.
- 03Put it on an alert route. Monitoring → Alert routes → add this channel as a step, usually the second tier: Slack first, PagerDuty when nobody acknowledges within the delay.
Fields
| Field | Required | What it is |
|---|---|---|
| Integration key | Yes | The routing_key of an Events API v2 integration. (32 hex characters) |
| Default severity | No | Used for report deliveries. Alerts carry their own. critical · error · warning · info |
What goes in Target
Not used. The destination service is decided by the integration key.
Target is optional for this channel. — not used
Test
Every channel has a Test button in the channel list (Settings → Channels). The result is kept — date, status and the provider's error when there was one — and a channel that was never tested is marked in the list.
Test triggers an "info" incident on the routing key's service and resolves it right away. You will see an incident resolved within seconds in the list — proof that the key reaches the right service.
Check it end to end
- 01Report: open a report, add this channel under Destinations (with the Target when the channel needs one), click Run now and open the run. The log says which channel each recipient went through and what the provider answered.
- 02Alert: under Monitoring → Alert routes, create a route with this channel as an escalation step. Routes match on severity and source; the first match wins.
- 03To fire an alert without breaking anything: create an HTTP monitor pointing at a URL that returns an error (for example https://httpstat.us/500) with a short interval. When it goes down the alert leaves through the route; delete the monitor afterwards. The message carries an acknowledge link — click it and the escalation stops.
- 04Report rules (new rows, value out of range) arrive through the same route, with source "report rule".
What most often goes wrong
The key must come from an “Events API v2” integration on a service — a REST API key or a v1 integration key is refused with 400. Severity here is the default for reports; alerts map their own severity (critical → critical, major → error, else warning).