PagerDuty
By PagerDuty, Inc.
PagerDuty is an incident response and on-call management platform that routes alerts from monitoring tools to the right person or team, automating escalation, scheduling, and post-incident workflows.
Definition
PagerDuty is an incident response and on-call management platform that routes alerts from monitoring tools to the right person or team, automating escalation, scheduling, and post-incident workflows.
Overview
PagerDuty, founded in 2009, was built around a specific operational pain point: monitoring tools are good at detecting problems, but someone still needs to be reliably notified and woken up when something breaks. PagerDuty sits between alerting sources — tools like Datadog, Splunk, Prometheus, or custom webhooks — and the humans who need to respond. At its core, PagerDuty ingests alerts, applies routing and deduplication rules, and pages the on-call engineer according to a defined schedule. If that person doesn't acknowledge the alert within a set window, PagerDuty automatically escalates to the next person or team, following an escalation policy. This structured approach is central to incident management, turning ad-hoc firefighting into a repeatable, auditable process. Beyond paging, PagerDuty has expanded into a broader incident response platform: it supports incident timelines, status pages, automated runbooks, postmortem tooling, and integrations with chat tools like Slack for coordinating responders during an outage. It's commonly deployed alongside monitoring and observability stacks as the layer that turns detection into action, a workflow discussed in SkillVeris's DevSecOps course. Its main competitor in on-call alerting is Opsgenie.
Key Features
- On-call scheduling with rotations, overrides, and time-zone-aware calendars
- Escalation policies that automatically page the next responder if an alert goes unacknowledged
- Event deduplication and noise reduction to avoid alert fatigue
- Deep integrations with monitoring, ticketing, and chat tools for automated alert ingestion
- Incident timelines and collaboration features for coordinating responders
- Automation actions and runbook triggers to remediate common issues
- Postmortem and analytics tooling for reviewing incident response performance
- Status page capabilities for communicating incidents to customers