Incident Management
PagerDuty Integration
Configure PagerDuty services to receive critical alerts from UptimePulse. Connect your monitoring to your on-call workflows in under five minutes.
Real-time monitoring for zero-downtime guarantees
Setup Steps
Follow these steps to link your UptimePulse account with PagerDuty. Once connected, any monitor that fails its health check will immediately trigger a PagerDuty incident routed to the correct on-call responder.
Step 1
Generate a PagerDuty Events API V2 Key
Log in to your PagerDuty account, navigate to Configuration > Services > New Service > Use our API directly. Copy the integration key (starts with a lowercase letter, e.g., 8f3a1c7b2e4d9f6a). You will need this in UptimePulse.
Step 2
Create a UptimePulse Webhook Destination
In UptimePulse, go to Settings > Integrations > Webhooks. Paste the PagerDuty integration key into the "PagerDuty Events API" field. Select your escalation policy from the dropdown — UptimePulse will auto-resolve PagerDuty incidents when the monitor recovers.
Step 3
Map Monitors to PagerDuty Services
Each UptimePulse monitor can be assigned to a specific PagerDuty service. Open any monitor's Alert Rules panel, enable "Send to PagerDuty," and choose the service. Critical monitors (e.g., api.uptimepulse.io, db-primary.internal) should map to your primary on-call rotation.
Step 4
Run a Test Incident
Click Fire Test Alert in the integration settings. A P3-severity incident should appear in PagerDuty within 15 seconds, with the title "UptimePulse: api.uptimepulse.io — HTTP 503" and full diagnostic metadata in the incident details. Confirm your on-call phone receives the notification.
Escalation Mapping
UptimePulse translates monitor severity levels into PagerDuty priorities and escalation tiers so your team responds at the right speed. The table below shows the default mapping — you can override it per-monitor.
Critical
PagerDuty P1 — Immediate
Triggers when a monitor returns HTTP 5xx, TLS certificate expires within 24 hours, or response time exceeds 5 seconds for 3 consecutive checks. Routes to your primary on-call rotation (e.g., SRE Team — Primary) with phone call + SMS. Auto-resolves when the monitor returns healthy for 2 consecutive checks.
Warning
PagerDuty P2 — Urgent
Triggers when response time exceeds 2 seconds for 5 consecutive checks, or when a secondary DNS endpoint fails. Routes to your secondary on-call rotation (e.g., SRE Team — Backup) with email + push notification. Auto-resolves after 10 consecutive healthy checks.
Info
PagerDuty P3 — Normal
Triggers for non-certificate expirations beyond 7 days, minor latency spikes, or successful deploy verifications. Routes to your engineering Slack channel via PagerDuty's Slack integration. No auto-resolution — these incidents remain open until manually acknowledged.
Need a custom escalation policy? Contact your account manager at integrations@uptimepulse.io or open a ticket in the UptimePulse help center under Incident Management > PagerDuty.