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 signed Events API webhooks. 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.
Availability: Available on Pro and Business plans (PagerDuty webhooks are categorized as a paid integration channel).
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 the PagerDuty channel in Uptimera
In Uptimera, Settings → Alert Channels → "Add PagerDuty". Paste the Events API key and pick a default severity (we recommend "error" for production).
- 3
Route monitors to PagerDuty
On each monitor, set the PagerDuty channel as a target. Uptimera will trigger incidents on detection, send acknowledgements when the incident is acked in Uptimera, and resolve them when the service recovers.
- 4
Verify with a test trigger
Click "Send test alert" — 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.
Auto-resolve on recovery
When Uptimera detects the service is back up, we send 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. Set per-monitor PagerDuty routing — only mark production monitors as PagerDuty targets. Non-critical monitors can still alert via Slack or email.
How does deduplication work?
Uptimera uses the monitor ID as the PagerDuty dedup_key, so a single flapping service produces one PagerDuty incident, not 20.
Ready to set this up?
Connect PagerDuty to Uptimera in under 2 minutes. Free plan included.