Developers / Guides
Route runtime auth-failure alerts into PagerDuty incidents.
Browse Documentation
Foundation
Platform
Capabilities
Product
Core Platform
Core Platform
Developers
Operations
Business
Billing and Plans
Billing and Plans
On This Page
No section anchors
# PagerDuty Escalation
Connect PagerDuty Events v2 when runtime auth-failure spikes should page an on-call rotation instead of landing in chat only.
## Setup
1. Open the runtime auth-failure panel in the developer dashboard.
2. Choose PagerDuty Events v2 as the destination type.
3. Keep the target URL at https://events.pagerduty.com/v2/enqueue unless you are using the EU endpoint.
4. Paste the PagerDuty routing key from the target service integration.
5. Set workspace or site scope and choose the minimum severity.
## Delivery Notes
- PagerDuty destinations send Events v2 trigger payloads directly.
- The console stores only a routing-key hint after save, not the full credential.
- PagerDuty destinations do not use x-cosantoir-signature and do not expose rotate-secret controls.
- Use the site-unavailable alert at high severity to page only on broken runtime wiring.