Incident management

PagerDuty Integration Guide

Send supported Uptimus monitor incidents to the PagerDuty services your team already uses, with regional installation for US and EU accounts.

Events API v2Simple InstallUS & EU regions

Overview

The PagerDuty integration routes monitor failures detected by Uptimus to one or more PagerDuty services. Uptimus creates a PagerDuty incident when an eligible monitor failure is detected and resolves the matching incident when that monitor recovers.

This integration uses PagerDuty Simple Install and Events API v2. It is not an OAuth integration, and you do not need to copy a client ID, client secret or access token into Uptimus.

1Uptimus detects a failureA monitor enters an incident state.

2Events API v2 receives itUptimus routes the event to the selected service.

3PagerDuty manages responseYour on-call workflow continues in PagerDuty.

Benefits

ResponseCreate incidents automaticallyTurn supported Uptimus monitor failures into actionable PagerDuty incidents.

RoutingChoose the right servicesConnect one or more PagerDuty services during the guided installation.

LifecycleResolve on recoveryUptimus resolves its matching PagerDuty incident after the monitor recovers.

RegionsUse US or EU PagerDutySelect the PagerDuty account region before starting Simple Install.

Requirements

Before you begin, make sure you have:

• an active Uptimus account and workspace;
• an active PagerDuty account in either the US or EU region;
• permission to add integrations to the PagerDuty services you select; and
• at least one PagerDuty service with an escalation policy configured.

Install PagerDuty

1. 1
   Sign in to Uptimus.

   Open the workspace where you want PagerDuty notifications to be delivered.

2. 2
   Open Integrations.

   Select Integrations from the workspace sidebar, then open PagerDuty.

3. 3
   Start the guided connection.

   Select Connect PagerDuty, then choose Install with PagerDuty.

4. 4
   Select the PagerDuty data region.

   Choose United States or Europe to match the region where your PagerDuty account is hosted.

5. 5
   Continue to PagerDuty.

   Sign in if requested, select the PagerDuty service or services, and approve the integration.

6. 6
   Return to Uptimus.

   Uptimus shows Confirming PagerDuty installation while it securely completes the connection.

7. 7
   Confirm the result.

   Look for PagerDuty connected and verify the expected services under PagerDuty services connected.

Choose the correct region

A US PagerDuty account cannot be installed through the EU flow, and an EU account cannot be installed through the US flow. If sign-in or service selection fails, return to Uptimus and select the other region.

How it works

PagerDuty returns account details and one integration key for each selected service to the Uptimus callback. Uptimus associates each destination with the workspace that started the installation and stores each integration key in encrypted credential storage.

For supported monitor lifecycle events, Uptimus sends these Events API v2 actions:

Uptimus state	PagerDuty action	Result
An eligible monitor failure is detected	trigger	Creates or updates the matching PagerDuty incident
The same monitor recovers	resolve	Resolves the matching PagerDuty incident

Uptimus uses a stable deduplication key so the trigger and recovery update the same PagerDuty incident. PagerDuty acknowledgement actions are not synchronized back to Uptimus, and Uptimus does not currently ingest PagerDuty incident changes. For PagerDuty's event model, see the official Events Integration functionality reference.

Test the integration

Check delivery without opening an incident

1. Open the connected PagerDuty integration in Uptimus.
2. In PagerDuty services, open the destination you want to verify.
3. Select Send test.
4. Uptimus displays Test queued and records the result in Recent activity.

The connection test validates that PagerDuty accepts an Events API v2 delivery. It intentionally sends a non-actionable resolve event, so it does not create a noisy PagerDuty incident.

Verify the full incident lifecycle

To verify trigger and recovery end to end, use a controlled test monitor:

1. Connect it to the PagerDuty destination you are testing.
2. Cause a planned failure and wait for Uptimus to confirm the incident state.
3. Confirm that PagerDuty creates an incident in the selected service.
4. Restore the endpoint and wait for Uptimus to confirm recovery.
5. Confirm that the matching PagerDuty incident is resolved.

Use a controlled monitor

This test can page an on-call responder. Use a dedicated test service or maintenance window and follow your team's incident-testing policy.

Configuration

From the connected PagerDuty page you can:

• view the selected destinations under PagerDuty services;
• inspect connection metadata under Details;
• validate a destination with Send test;
• review delivery and connection changes in Recent activity;
• temporarily set a destination to Paused and return it to Active;
• add or update destinations with Change service; and
• remove one destination with Disconnect service.

The current integration sends all eligible PagerDuty notifications to every active connected destination. Per-alert, per-monitor and per-severity routing rules are not currently exposed on this integration page.

When you use Change service, PagerDuty returns the services selected in the new install flow. Disconnect any destination you no longer want Uptimus to use.

Disconnect or uninstall

Disconnect from Uptimus

1. Open Integrations and select the connected PagerDuty integration.
2. Open the destination under PagerDuty services.
3. Select Disconnect service and confirm.

Uptimus revokes the local destination, stops future notifications to it and retains the non-secret activity history needed for auditability. Existing PagerDuty incidents are not deleted or modified by disconnecting.

Remove the integration from PagerDuty

Open the corresponding service in PagerDuty, select Integrations, locate the Uptimus Events API v2 integration and remove it. Removing it directly in PagerDuty does not notify Uptimus, so disconnect the matching destination in Uptimus as well. If the two sides no longer match, disconnect and reconnect the service.

Troubleshooting

PagerDuty sign-in or service selection does not open

Confirm that you selected the correct United States or Europe data region, then start Install with PagerDuty again.

No PagerDuty services are available

Confirm that at least one service exists and that your PagerDuty role can add integrations to it. Ask a PagerDuty administrator if service integration controls are unavailable.

PagerDuty returns to Uptimus but does not connect

Keep the callback page open until confirmation finishes. If it reports a failure, return to PagerDuty in Uptimus and restart the install flow. Do not reuse an old callback URL.

Send test does not create an incident

This is expected: Send test checks delivery with a non-actionable resolve event. Use the controlled monitor lifecycle steps above when you need to verify incident creation.

A real monitor failure does not create an incident

Confirm the destination is Active, review Recent activity, check the selected PagerDuty service and escalation policy, then reconnect the service if the integration was removed or rotated in PagerDuty.

The integration was removed directly from PagerDuty

Disconnect the stale destination in Uptimus, select Change service or Connect PagerDuty, and complete Simple Install again.

Security and privacy

During Simple Install, Uptimus receives PagerDuty account metadata, the selected service metadata and an integration key for each destination. Integration keys are encrypted with AES-256-GCM before being stored and are never returned by the workspace connection API.

For supported incidents, Uptimus sends PagerDuty the event action, incident summary, source, severity, stable deduplication key and relevant monitor details. Uptimus does not request PagerDuty OAuth access tokens for this integration.

You can revoke delivery by disconnecting the destination in Uptimus and removing the integration from its PagerDuty service. See the Uptimus Privacy Policy and Terms of Service for the product-wide data terms.

Support

If the installation still fails, include the Uptimus workspace, PagerDuty data region, approximate time and visible error message in your request. Never send an integration key or callback payload.

• Email contact@uptimus.app
• Open the Uptimus support portal

App details

Field	Value
PagerDuty app	Uptimus
App ID	PPC5O62
Installation	PagerDuty Simple Install
Event delivery	PagerDuty Events API v2
Supported regions	United States and Europe