Connect PagerDuty (Events API v2)

Trigger, acknowledge and resolve PagerDuty incidents from Uptime Tracker with an Events API v2 routing key, with the failure reason in custom details. Team plan.

Updated By the Uptime Tracker team
  1. Add an Events API V2 integration in PagerDutyOpen the PagerDuty service, go to its Integrations tab, add an integration and choose Events API V2.
  2. Copy the integration keyCopy the 32-character Integration Key shown for the new integration.
  3. Add the destinationIn Uptime Tracker, go to Integrations → Add destination and choose "Set up PagerDuty". Pick the Events API region and paste the Integration (routing) key.
  4. SaveChoose "Add destination".
  5. Send a testChoose "Send test" and confirm. A [TEST] alert with info severity is triggered and resolved automatically a moment later.

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 Pro the PagerDuty card shows Needs Team.
  • Permission in PagerDuty to add integrations to a service.

Get the integration (routing) key in PagerDuty

  1. In PagerDuty, open Services → Service Directory and pick the service that should be paged (or create one).
  2. Open the service's Integrations tab and choose Add an integration (or Add another integration).
  3. Choose Events API V2 and add it.
  4. 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

  1. Go to Integrations → Add destination, find PagerDuty and choose Set up PagerDuty.
  2. Enter a Name.
  3. 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).
  4. Paste the Integration (routing) key. It is stored encrypted and never shown again.
  5. Choose Add destination.

How alerts map to PagerDuty

In Uptime TrackerIn PagerDuty
Monitor down (incident opens)Trigger, severity critical
Reminder or escalation stepTrigger with the same key, de-duplicated into the open incident
Incident acknowledgedAcknowledge
Monitor recoveredResolve

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.

What the PagerDuty alert contains

The alert summary carries the title, the time and the Reason: line, and the component is the monitor name. The alert's custom details list event_type, monitor, target (the redacted host), incident_id and failure_reason, such as HTTP 503 Service Unavailable, so you can use them in PagerDuty Event Orchestration rules.

Test it

Choose Send test. A confirmation explains what happens; confirm to send. The test triggers a PagerDuty alert titled "[TEST] Uptime Tracker test notification" with info severity and a separate de-duplication key, then resolves it automatically a moment later, so no test incident is left open. Depending on the service's urgency rules (for example, if every alert is high urgency rather than based on severity), on-call responders may still be notified once, so tell your team before testing. If the automatic resolve fails, Integrations → Deliveries says so and you can resolve the test alert in PagerDuty.

Change the region or key

Choose Edit connection on the destination. Pick a different Events API region (or Keep the current region) and/or enter a new Integration (routing) key, then choose Save connection. The key is checked like a new one, and saving re-enables a destination that was disabled after delivery failures.

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.
  • "PagerDuty rejected the event (HTTP 400): …": PagerDuty did not accept the routing key or the event, often because the key was deleted or belongs to an account in the other region. PagerDuty's own message is shown after the colon. This is not retried: the destination is disabled at once and the workspace is told through its other destinations. Correct the key or region with Edit connection; saving re-enables it.
  • 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.
FAQ

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, or switch the region later with Edit connection.

Will Send test page my on-call engineer?

It sends a [TEST] alert with info severity and resolves it automatically. Depending on the service's urgency rules, responders may still be notified once, so warn your team first.

Uptime Tracker

Start monitoring in under five minutes

Start on the free plan — commercial use allowed. No credit card required.

  • Free forever plan
  • No credit card
  • Cancel anytime