- Add an Events API V2 integration in PagerDutyOpen the PagerDuty service, go to its Integrations tab, add an integration and choose Events API V2.
- Copy the integration keyCopy the 32-character Integration Key shown for the new integration.
- Add the destinationIn Uptime Tracker, go to Integrations and choose "Set up PagerDuty". Pick the Events API region and paste the Integration (routing) key.
- SaveChoose "Add destination".
- Test, then resolve the testChoose "Send test". It opens a real PagerDuty incident, which you resolve in PagerDuty.
If your team already runs on-call in PagerDuty, Uptime Tracker can open, acknowledge and resolve PagerDuty incidents for you. The integration uses PagerDuty's Events API v2 and is available on the Team plan (and the Team trial).
Before you start
- A workspace on Team. On Free and Starter the PagerDuty card shows Needs Team.
- Permission in PagerDuty to add integrations to a service.
Get the integration (routing) key in PagerDuty
- In PagerDuty, open Services → Service Directory and pick the service that should be paged (or create one).
- Open the service's Integrations tab and choose Add an integration (or Add another integration).
- Choose Events API V2 and add it.
- Expand the new integration and copy its Integration Key, 32 letters and digits.
A 32-character routing key from PagerDuty Event Orchestration works the same way. Do not use a REST API key; it has a different format and is refused.
Add it in Uptime Tracker
- Go to Integrations, find PagerDuty and choose Set up PagerDuty.
- Enter a Name.
- Pick the Events API region: United States (events.pagerduty.com), or European Union (events.eu.pagerduty.com) only if your PagerDuty account is hosted in the EU (its address ends in
.eu.pagerduty.com). - Paste the Integration (routing) key. It is stored encrypted and never shown again.
- Choose Add destination.
How alerts map to PagerDuty
| In Uptime Tracker | In PagerDuty |
|---|---|
| Monitor down (incident opens) | Trigger, severity critical |
| Reminder or escalation step | Trigger with the same key, de-duplicated into the open incident |
| Incident acknowledged | Acknowledge |
| Monitor recovered | Resolve |
Each Uptime Tracker incident uses its incident id as the PagerDuty de-duplication key, so retries never open duplicates. The sync is one-way: acknowledging or resolving in PagerDuty does not change the incident in Uptime Tracker.
Test it
Send test triggers a real, separate PagerDuty incident titled "Test notification", which may page whoever is on call for that service. Warn your team first, and resolve the test incident in PagerDuty afterwards.
Troubleshooting
- "The referenced secret is not a valid pagerduty credential": the key must be exactly 32 letters and digits. Copy the Integration Key of an Events API V2 integration, not a REST API key.
- HTTP 400 in the Deliveries tab: PagerDuty did not accept the key, often because the region is wrong. Add a new destination with the correct region and delete the old one.
- Nothing is paged: check that the destination is used. Without routing rules every verified shared destination receives alerts; with rules, the PagerDuty destination must be in a matching rule or escalation step.
Frequently asked questions
Which plan includes PagerDuty?
The Team plan, including the 14-day Team trial.
Does acknowledging in PagerDuty acknowledge the incident in Uptime Tracker?
No. The integration is one-way: Uptime Tracker triggers, acknowledges and resolves PagerDuty incidents, but changes made in PagerDuty are not sent back.
Will PagerDuty get duplicate incidents for reminders?
No. Every event for one incident uses the same de-duplication key, so PagerDuty folds them into one incident.
Does it work with an EU PagerDuty account?
Yes. Choose the European Union (events.eu.pagerduty.com) region when adding the destination.
