PagerDuty Integration
The PagerDuty integration connects AtlasAI with your PagerDuty account for bidirectional incident synchronization and on-call schedule awareness. AtlasAI can trigger PagerDuty incidents, and PagerDuty alerts can flow into AtlasAI for AI-powered analysis.
Prerequisites
- A PagerDuty account with admin access
- A PagerDuty API key (v2) with read/write permissions
Setup
Step 1: Generate a PagerDuty API key.
In PagerDuty, navigate to Configuration → API Access and create a new API key with full access.
Step 2: Configure the integration in AtlasAI.
- Navigate to Settings → Integrations → PagerDuty
- Click Add Connection
- Enter your credentials:
- API Key: Your PagerDuty v2 API key
- Default Service: The PagerDuty service to use for outbound incidents
- Configure sync options:
- Inbound incidents: Import PagerDuty incidents into AtlasAI
- Outbound incidents: Create PagerDuty incidents from AtlasAI
- On-call sync: Import on-call schedules and escalation policies
- Click Test Connection and then Save & Enable
Step 3: Configure event routing.
Navigate to Settings → Integrations → PagerDuty → Routing Rules to define which AtlasAI incidents trigger PagerDuty pages:
- Route by severity (e.g., only P1 and P2 create PagerDuty incidents)
- Route by service (e.g., only production services)
- Route by team (e.g., different PagerDuty services per team)
Features
On-Call Awareness
AtlasAI imports your PagerDuty on-call schedules and displays the current on-call engineer in incident views and the Command Center. The AI Copilot knows who is on call and can mention them in incident summaries.
Bidirectional Status Sync
- When a PagerDuty incident is acknowledged, the AtlasAI incident status updates to “In Progress”
- When an AtlasAI incident is resolved, the linked PagerDuty incident is auto-resolved
- Notes and timeline entries sync between both platforms
Smart Paging
AtlasAI uses AI confidence scores to prevent unnecessary pages. If the AI determines an issue is likely a false positive or auto-resolvable, it can suppress the PagerDuty notification (configurable per trust level).
Troubleshooting
| Issue | Solution |
|---|---|
| API key rejected | Ensure the key has full access permissions |
| Incidents not syncing | Check routing rules and verify the target PagerDuty service exists |
| On-call not showing | Verify the on-call sync is enabled and the schedule IDs are correct |
| Duplicate pages | Review routing rules for overlapping conditions |