Benefits
- Page the on-call engineer the moment a monitor fails, through the escalation policy you already run.
- No manual close: the recovery resolves the incident it opened, matched by a dedup key per monitor and region.
- A failure in one region pages once for that region, so a regional outage is told apart from a global one.
- Works on every RealUptime plan, Free included.
How it works
- When a monitor goes down in a region, RealUptime sends a
triggerevent to the PagerDuty Events API v2 with severitycritical, sourcerealuptimeand a summary naming the monitor and region. - When that region recovers, RealUptime sends a
resolveevent with the same dedup key. - PagerDuty delivery runs beside email, Slack and webhooks. A PagerDuty delivery problem never delays the other channels, and failed deliveries are retried.
Requirements
- A RealUptime account (free to create at realuptime.io) with at least one monitor.
- A PagerDuty account with permission to add an integration to a service (Manager, Admin or Account Owner role).
Support
For help with this integration, contact support@realuptime.io or use realuptime.io/support.
Integration walkthrough
In PagerDuty
- Go to Services > Service Directory and open the service that should receive RealUptime incidents, or create one.
- On the Integrations tab, select Add an integration, search for RealUptime (or choose Events API V2), and select Add.
- Expand the new integration and copy its Integration Key.
In RealUptime
- Sign in and open Account > Alert channels, then the PagerDuty section.
- Paste the key into Integration key and select Save.
- Select Send test to open a test incident in PagerDuty and confirm the connection.
- Every monitor alerts PagerDuty by default. To send only some monitors, add an alert routing rule under Monitor > Settings.
How to uninstall
- In RealUptime, open Account > Alert channels and select Remove in the PagerDuty section. Alerts to PagerDuty stop immediately.
- In PagerDuty, open the service's Integrations tab and delete the RealUptime integration.
FAQ
An incident did not open. What should I check?
Confirm the PagerDuty section shows a saved key, use Send test, and check that no alert routing rule leaves PagerDuty out for that monitor.
Why did resolving the incident in PagerDuty not stop the next page?
RealUptime opens a new incident each time a monitor goes down again. Resolving in PagerDuty closes that incident only; it does not pause the monitor.