PagerDuty Integration | StatusPulse
Real-time monitoring for zero-downtime SaaS
Route critical uptime failures directly to your on-call engineers. The StatusPulse–PagerDuty webhook sync eliminates manual triage, ensuring sub-30-second alert propagation for production outages across your AWS and GCP infrastructure.
Connect PagerDuty Account View API ReferenceSetup Steps
1. Generate PagerDuty Integration Key
Log into your PagerDuty dashboard at app.pagerduty.com, navigate to Services > Create Service, and select "Use our API directly" as the service type. Copy the unique Integration Key (e.g., 8a7b3c9d2e1f) from the configuration panel.
2. Configure StatusPulse Webhook Endpoint
In StatusPulse, open Settings > Integrations > PagerDuty. Paste your Integration Key into the designated field and set the event severity threshold to "Critical" and "High". Enable "Include Custom Metrics" to pass CPU and memory snapshots with each trigger.
3. Validate Connection & Test Alert
Click "Verify Integration" to run a handshake test. StatusPulse will push a synthetic "test_trigger" event to your PagerDuty routing layer. Confirm receipt in your PD activity log and assign the service to your primary on-call rotation.
Escalation & Event Mapping
Automate incident lifecycle management by aligning StatusPulse health checks with PagerDuty escalation policies. Our native mapping ensures seamless transition from detection to resolution without manual context switching.
Event Severity Mapping
StatusPulse translates HTTP 5xx, SSL expiry <14 days, and TCP timeout failures into PagerDuty "critical" and "warning" severities. Custom downtime windows automatically suppress alerts during scheduled maintenance for deployments like US-EAST-1 or EU-WEST-2.
Auto-Resolution Handling
When a monitored endpoint recovers, StatusPulse dispatches a "resolve_event" payload containing the exact downtime duration, recovery timestamp, and final response code. PagerDuty automatically closes the incident and logs the resolution for post-mortem analysis.
Escalation Policy Sync
Link your StatusPulse checks to specific PagerDuty escalation layers. If Tier 1 engineers (e.g., DevOps Alpha) do not acknowledge within 15 minutes, alerts automatically route to Tier 2 (SRE Management) with enriched context logs and runbook URLs.
Need to modify routing rules or adjust acknowledgment timers? Access the advanced webhook configuration in your StatusPulse account under Settings > Integrations > PagerDuty > Advanced Mapping. Contact support@statuspulse.io if you require custom JSON payload templates for legacy PD instances.