PagerDuty Connection

Connects your agent to PagerDuty for incident management. Query incidents, check on-call schedules, view alert details, and manage incident status. Write operations (acknowledge, resolve) require confirmation.

Authentication

API token (v2). Generate from Configuration > API Access Keys.

• token — PagerDuty REST API v2 token
• from_email — Email address for write operations (used as actor)

Endpoints

Incidents

• GET /incidents — List incidents with filters (status, urgency, service, date range)
• GET /incidents/{id} — Get incident details with timeline
• GET /incidents/{id}/log_entries — Get incident log entries (full timeline)
• PUT /incidents/{id} — Update incident status (requires confirmation)
• POST /incidents/{id}/notes — Add note to incident

Alerts

• GET /incidents/{id}/alerts — List alerts grouped under an incident
• GET /alerts/{id} — Get alert detail with raw payload

Services

• GET /services — List services with status
• GET /services/{id} — Get service detail and integrations

On-Call

• GET /oncalls — List current on-call users by schedule/policy
• GET /schedules/{id} — Get schedule with overrides

Escalation Policies

• GET /escalation_policies — List escalation policies with rules

Rules

• Incident acknowledge/resolve always require confirmation
• Rate limit: 900 requests/minute (PagerDuty standard)
• The agent includes timezone context for on-call lookups
• Bulk incident operations (>3) require itemized confirmation