PagerDuty Integration
Route Kestrel incidents to PagerDuty with full root cause analysis, AI-generated fixes, and automatic resolution when remediations are applied.
When something breaks in production, your team is already working in PagerDuty. Now Kestrel meets them there. The PagerDuty Integration connects Kestrel's AI-powered incident response directly to your existing on-call workflows - so the engineer who gets paged also gets the root cause and the fix.
Incidents That Actually Help You
Most PagerDuty alerts tell you something is wrong. Kestrel tells you why it's wrong and how to fix it. When Kestrel detects an incident in your Kubernetes clusters or cloud infrastructure, it automatically creates a PagerDuty incident that includes:
- Full root cause analysis with the chain of events that led to the failure
- Affected resources, severity, and blast radius
- AI-generated remediation steps with ready-to-apply fixes
- Direct links to the Kestrel dashboard for deeper investigation
Bidirectional Sync
Kestrel and PagerDuty stay in sync throughout the incident lifecycle:
- Incident Creation
Kestrel detects an issue and creates a PagerDuty incident on the correct service with the right severity. Your existing escalation policies and on-call schedules are respected.
- Live Updates
As Kestrel's investigation progresses, the PagerDuty incident is updated with new findings. If the root cause changes or additional affected resources are discovered, your team sees it immediately.
- Automatic Resolution
When a fix is applied through Kestrel (via the dashboard, Slack, or API) and validated, the corresponding PagerDuty incident is automatically resolved with a summary of what was done.
Service Mapping
Map your Kubernetes namespaces, clusters, and cloud accounts to specific PagerDuty services. When Kestrel detects an incident affecting your payments namespace, the alert goes to the payments team's PagerDuty service - not a generic catch-all.
You can configure mappings at multiple levels:
- Cloud account → PagerDuty service
- Kubernetes cluster → PagerDuty service
- Namespace → PagerDuty service
- Specific workload labels → PagerDuty service
Noise Reduction
Kestrel doesn't just forward every event to PagerDuty. It correlates related signals, filters transient issues, and only pages your team for incidents that require human attention. Brief pod restarts, CSP maintenance windows, and other known-benign events are classified and suppressed automatically.
The result: fewer pages, and the ones you do get come with everything you need to resolve the issue.
Getting Started
Connect PagerDuty from the Integrations page in your Kestrel dashboard. Authorize the integration with your PagerDuty account, map your services, and you're live. Kestrel uses PagerDuty's Events API v2, so incidents appear with full context in your existing workflows.