Bridge Uptimera detection with your existing on-call
Most engineering teams already pay for PagerDuty. Uptimera handles fast multi-region detection; PagerDuty handles paging, escalation, and your rotation schedule.
On-call integration
Uptimera + PagerDuty
Forward Uptimera incidents to PagerDuty via the Events API v2. PagerDuty's escalation policies, on-call rotations, and acknowledgement workflow take over — you keep Uptimera as the source of truth for what's actually down, and recoveries resolve the PagerDuty incident automatically.
Availability: Available on the Business plan — delivered through a webhook alert channel, which is a Business-plan feature. Free and Pro plans use email and Slack.
Setup
- 1
Create an Events API v2 integration in PagerDuty
In PagerDuty, go to Services → your service → Integrations → "Add an integration" and pick "Events API v2". Copy the Integration Key.
- 2
Add a PagerDuty webhook channel in Uptimera
In Uptimera, open Alerts → Add Channel → Webhook, then set the Format to "PagerDuty". Paste the Integration (routing) key. You can leave the URL blank to use PagerDuty's default Events API endpoint.
- 3
Attach it to your production monitors
Add the PagerDuty channel to the monitors that should page. Uptimera triggers a PagerDuty incident when the monitor goes down and resolves it automatically when the service recovers.
- 4
Verify with a test trigger
Click "Test" on the channel card — a PagerDuty incident should appear within a few seconds and route through your normal on-call policy.
What teams do with this
Quiet hours for non-prod monitors
Use PagerDuty's schedules to enforce business-hours-only paging for staging monitors while production stays 24/7. Uptimera's own per-channel business-hours window can suppress non-urgent alerts too.
Auto-resolve on recovery
When Uptimera detects the service is back up, it sends a resolve event automatically — your on-call doesn't have to manually close PagerDuty incidents.
Common questions
Is this Events API v1 or v2?
Events API v2. v1 has been deprecated by PagerDuty since 2021. If your service still has a v1 routing key, create a new v2 integration alongside it.
Can I forward only critical incidents?
Yes. Routing is per monitor — only attach the PagerDuty channel to the monitors that should page. Non-critical monitors can still alert via Slack or email by attaching those channels instead.
How does deduplication work?
Uptimera sends the incident id as the PagerDuty dedup_key. A single ongoing outage is one PagerDuty incident, and the recovery event resolves exactly the incident it opened.
Ready to set this up?
Connect PagerDuty to Uptimera in under 2 minutes. Free plan included.