PagerDuty Integration
Connect StatusPulse to PagerDuty in under three minutes. Automatic incident creation, intelligent escalation, and real-time resolution sync — no webhooks or custom scripts required.
Start Integration Read the DocsSetup
Bridge StatusPulse monitoring with PagerDuty's incident management platform. When any monitored endpoint drops below your defined SLA threshold, PagerDuty creates a fully enriched incident — complete with runbook links, affected service tags, and on-call routing — automatically.
1. Generate an Integration Key
In your PagerDuty dashboard, navigate to Services > Add Service. Choose "Use our API directly" and copy the generated Integration Key. This is a read-write token scoped to the selected service account.
2. Link from StatusPulse
Go to Integrations > PagerDuty in your StatusPulse control panel. Paste the Integration Key, select your target PagerDuty service, and map your StatusPulse monitors to PagerDuty service tiers (e.g., "API Gateway" → P1, "Blog CDN" → P3).
3. Define Alert Thresholds
Set per-monitor trigger rules: consecutive failure count (default 2), response time thresholds (e.g., >2,000 ms for 3 cycles), and HTTP status exclusions (ignore 503s during maintenance windows). Each rule maps to a PagerDuty severity level.
Once linked, StatusPulse pushes events to PagerDuty via the Events API v2. Latency between detection and incident creation averages 1.2 seconds. All payloads include monitor_id, region, last_healthy_timestamp, and a direct link to the StatusPulse incident timeline.
Escalation Policies
PagerDuty escalation policies drive who gets paged and when. StatusPulse respects your existing policy chains — you don't need to rebuild routing logic. We enrich incidents with context so your on-call engineers triage faster.
Automatic Severity Mapping
Critical monitors (payment gateways, auth endpoints) trigger Critical severity incidents, routing to your P1 on-call rotation within 60 seconds. Warning monitors (asset CDNs, non-critical APIs) create Warning severity incidents, escalating to P2 after 15 minutes without acknowledgment.
Runbook & Context Injection
Every PagerDuty incident created by StatusPulse includes a custom field block: the affected monitor's URL, the last successful response body hash, a link to your internal runbook (configured per monitor), and a summary of the last 10 health checks leading up to the failure.
Multi-Service Correlation
When multiple monitors fail simultaneously (e.g., API + Database + Auth), StatusPulse groups them into a single PagerDuty incident with a "compound outage" tag. This prevents alert fatigue during cascading failures and keeps your incident commander focused on root cause, not noise.
Escalation timing is fully controlled by your PagerDuty policy. StatusPulse does not override acknowledgment or resolution timers. If an incident is acknowledged in PagerDuty, StatusPule suppresses duplicate Slack or email notifications for that event.
Resolution Sync
When your team resolves an incident in PagerDuty, StatusPulse automatically marks the corresponding monitoring event as resolved. This keeps your uptime dashboards, status pages, and SLA reports accurate without manual intervention.
Bidirectional State Sync
Resolution in PagerDuty pushes a resolve_event back to StatusPulse via the Events API. The monitor's state flips from "down" to "recovering," and after two consecutive successful checks, it transitions to "healthy." Total sync latency averages under 800 ms.
Automatic SLA Recalculation
Once resolved, StatusPulse recalculates your monthly SLA percentages in real time. If a payment endpoint was down for 4 minutes and 12 seconds, that downtime is subtracted from your 99.95% SLA commitment. Your status page reflects the updated uptime within one minute.
Post-Incident Reporting
Every resolved incident generates a report in StatusPulse including: total downtime duration, affected regions, number of automated notifications sent, and a timeline of health checks. Export to PDF or push to your incident database (Jira, Vanta, or internal wiki) with one click.
Resolution notes from PagerDuty are stored alongside the StatusPulse incident record. During quarterly reviews, you can filter all PagerDuty-linked incidents by severity, resolution time, or monitor group to identify recurring failure patterns and adjust alert thresholds accordingly.