- Home
- Integrations
- PagerDuty
PagerDuty: page the on-call engineer, resolve on recovery
Paste a PagerDuty Events API v2 routing key and Tenium opens an incident on down and resolves it on up, keyed to the same incident so you never get duplicates. Your schedules and escalation policies stay in PagerDuty.
Down
Triggeredcritical
DOWN · Client A shop: Client A shop · HTTP 503 Service Unavailable · confirmed from Amsterdam (AMS), London (LON)
| Source | https://shop.clienta.com |
| Action | event_action: trigger |
| Dedup key | incident id e5b4… |
Back up
Resolvedinfo
UP · Client A shop: Client A shop is back up after 4m 12s
| Source | https://shop.clienta.com |
| Action | event_action: resolve |
| Dedup key | incident id e5b4… |
SSL expiry
Triggeredwarning
SSL EXPIRES IN 7 DAYS · Client A shop: SSL certificate for Client A shop expires in 7 days
| Source | https://shop.clienta.com |
| Action | event_action: trigger |
| Dedup key | incident id e5b4… |
Heartbeat missed
Triggeredcritical
MISSED · Nightly backup: Nightly backup · No ping received for 26 min
| Source | heartbeat: nightly-backup |
| Action | event_action: trigger |
| Dedup key | incident id e5b4… |
Simulation: nothing is sent from this page.
Set it up
- 1
Add an Events API v2 integration
In PagerDuty open the service, Integrations, add Events API v2 and copy the integration (routing) key.
PagerDutySaved - 2
Paste the key and press Test
Open Integrations, choose PagerDuty, paste the routing key, save and press Send test. An event reaches your service.
Save the contact first
- 3
Attach it to the monitors that matter
Attach it to production monitors only. Add an alert delay on Pro or higher to page PagerDuty only if the first channel is not acknowledged.
Save the contact first
Interactive mock, nothing is saved.
What is in the message
- trigger on down, resolve on up, with a dedup key per incident
- A summary with the status and monitor name, and the target as source
- Severity: critical for down, warning for degraded and expiry
Alert text is generated by Tenium and is currently English.
Plan and limits
- Available from Agency ($59/month)
- Included onAgency
- Outbound alerts per hour on your planFree 40 · Starter 300 · Pro 1,500 · Agency 6,000
- Alert delay before sendingAvailable on Pro and Agency
Good to know
- Tenium sends events; schedules, escalation policies and mobile push stay in PagerDuty.
- The routing key is 16 to 64 letters and digits.
How alerts and escalation work
Contacts, routing, delays and acknowledgement are explained in the docs.
PagerDuty FAQ
Does Tenium resolve the PagerDuty incident automatically?
Yes. A recovery sends a resolve event with the same dedup key as the trigger, so the PagerDuty incident closes itself.
Which PagerDuty key do I need?
The integration key (routing key) of an Events API v2 integration on a PagerDuty service. It is not an API token.
Do I get phone calls or SMS from Tenium?
No. Tenium has no SMS and no voice calls of its own. If you need phone paging, PagerDuty can do it from the event we send.
Which plan includes PagerDuty?
PagerDuty is available from the Agency plan ($59/month) and on every plan above it.
How do I test PagerDuty alerts?
Open Settings, Contacts and press Send test next to the contact. A message labelled TEST arrives within seconds. Add at least one monitor first, because the checker sends the alerts.
Can I delay PagerDuty until nobody has reacted?
Yes, on Pro and Agency. Give the contact an alert delay in minutes: it fires only if the incident is still open then, and acknowledging the incident cancels it.
Connect your first channel in a minute
Start free with email, Discord and Google Chat. 30 monitors, no card.