PagerDuty Integration
Automated PagerDuty incident creation, escalation, and auto-resolution with AI-enriched context. Every page includes the root cause summary, trace links, and runbook suggestions before the engineer even picks up.
How It Works
Create a PagerDuty Service
In PagerDuty, create a new Service or use an existing one. Generate an Integration Key (Events API v2). This key is used by TigerOps to post incidents.
Add the Integration in TigerOps
Paste the PagerDuty Integration Key into TigerOps under Integrations > PagerDuty. Map TigerOps alert severities to PagerDuty urgency levels.
Configure Escalation Rules
Define which TigerOps alert policies trigger PagerDuty incidents. Route critical SLO breaches to one service, infrastructure alerts to another.
Incidents are Automatically Enriched
TigerOps sends AI-generated incident summaries, trace links, dashboard URLs, and runbook suggestions directly in the PagerDuty incident body.
What You Get Out of the Box
Events API v2 Integration
Uses PagerDuty Events API v2 for reliable incident creation, acknowledgment, and resolution with deduplication keys to prevent duplicate pages.
AI-Enriched Incident Bodies
Every PagerDuty incident includes an AI-generated summary of what broke, suspected root cause, affected services, and a link to the TigerOps investigation.
Bidirectional Sync
Acknowledgments and resolutions made in PagerDuty are reflected in TigerOps in real time. Resolve an incident in TigerOps and PagerDuty closes automatically.
Multi-Service Routing
Route different alert types to different PagerDuty services — database alerts to the DBA on-call, app errors to the app team, infra to the platform team.
Severity Mapping
Map TigerOps severity levels (critical, warning, info) to PagerDuty urgency (high, low) and priority (P1–P5) automatically per alert policy.
Auto-Resolve on Recovery
When TigerOps detects that an incident has recovered, it automatically sends a resolve event to PagerDuty — no manual cleanup required.
PagerDuty Alert Policy
Example TigerOps alert policy routing critical incidents to PagerDuty with AI enrichment.
# TigerOps Alert Policy — PagerDuty Routing
alert_policies:
- name: "SLO Breach → Page On-Call"
conditions:
- type: slo_breach
threshold_pct: 99.9
- type: error_rate_spike
multiplier: 5.0
severity: critical
notification_channels:
- type: pagerduty
integration_key: "${PAGERDUTY_INTEGRATION_KEY}"
urgency: high
priority: P1
# AI enrichment included automatically
include_ai_summary: true
include_trace_link: true
include_runbook: true
# Auto-resolve when metrics recover
auto_resolve: true
resolve_after_minutes: 5
- name: "Infrastructure Warning → Low Urgency"
conditions:
- type: cpu_high
threshold_pct: 85
- type: memory_high
threshold_pct: 90
severity: warning
notification_channels:
- type: pagerduty
integration_key: "${PAGERDUTY_INFRA_KEY}"
urgency: low
priority: P3
auto_resolve: trueCommon Questions
Does TigerOps use PagerDuty Events API v1 or v2?
TigerOps uses Events API v2 exclusively. This is the current PagerDuty standard and supports deduplication keys, full incident enrichment, and the latest alert urgency/priority features. If you have older v1 integrations, we recommend migrating to v2.
Can TigerOps resolve PagerDuty incidents automatically?
Yes. When TigerOps detects that the conditions triggering an incident have resolved (metrics returned to normal, AI SRE confirms recovery), it sends a resolve event to PagerDuty using the same dedup_key — closing the incident without human action.
Can I map TigerOps severities to PagerDuty priorities?
Yes. In the integration configuration, you can map TigerOps severity levels to PagerDuty urgency (high/low) and priority (P1–P5). This ensures critical SLO breaches always trigger high-urgency pages with P1 priority.
Does TigerOps support PagerDuty's Stakeholder notifications?
Indirectly — when TigerOps creates a high-priority PagerDuty incident, PagerDuty's own stakeholder notification features (Status Updates, Business Services) work as usual. TigerOps does not integrate with stakeholder APIs directly.
Can I use multiple PagerDuty services from one TigerOps workspace?
Yes. You can configure multiple PagerDuty integration keys (one per PagerDuty service) in TigerOps and route different alert policies to different services. This is the recommended way to separate on-call rotations by team.
Wake Up Your On-Call with Context, Not Noise
No credit card required. AI-enriched pages. Auto-resolve built in.