PagerDuty
Incident management and on-call alerting platform that routes alerts to the right responders, manages escalations, and tracks incident lifecycle via REST API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforced. API tokens should be scoped to service accounts. OAuth2 scopes limit access surface. Webhook signatures use HMAC-SHA256 — verify before processing.
⚡ Reliability
Best When
You have multi-team on-call rotations with complex escalation policies and need reliable, auditable incident lifecycle management.
Avoid When
Your team is fewer than 5 people and you need basic alerting without escalation policies or incident tracking workflows.
Use Cases
- • Programmatically trigger incidents from monitoring or agent-detected anomalies using the Events API v2
- • Query on-call schedules to determine the current responder and send context-enriched pages without navigating the UI
- • Acknowledge and resolve incidents automatically when an agent detects that an underlying issue has self-healed
- • Attach runbook steps or diagnostic context to open incidents via the incident notes or custom fields API
- • Extract incident history and MTTD/MTTR metrics for postmortem reporting and SLO tracking pipelines
Not For
- • Simple uptime monitoring without incident routing — a lightweight tool like BetterStack suffices
- • Alerting for solo developers or very small teams where the pricing and complexity overhead is not justified
- • Real-time log streaming or APM — PagerDuty receives alerts but does not replace observability tools
Interface
Authentication
API tokens (user or service account) for server-side agent use. OAuth2 available for user-delegated access. Events API v2 uses a separate integration key (routing key) for event ingestion.
Pricing
Free tier is suitable for small teams. AIOps and advanced analytics features are Enterprise-only. Annual billing discounts available.
Agent Metadata
Known Gotchas
- ⚠ Events API v2 and REST API use different authentication — Events API uses a routing_key (integration key), REST API uses Authorization: Token token=...; mixing them causes silent 400 errors
- ⚠ dedup_key in Events API is essential for agents — omitting it causes duplicate incidents on retries; key should be deterministic based on the source alert fingerprint
- ⚠ Incident acknowledgement auto-expires after a configurable timeout (default 30 min) and re-notifies; agents that ack without resolving must account for re-escalation
- ⚠ On-call schedule queries return the user on-call at query time — agents must pass a since/until window to get schedules for future or past periods
- ⚠ Webhook v3 payloads are structured differently from v2 — verify webhook version when building event processors; v2 is deprecated but still active on older integrations
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for PagerDuty.
Scores are editorial opinions as of 2026-03-06.