# PagerDuty

Incident response on PagerDuty — triage and manage incidents (list, get, notes, create, acknowledge/resolve) and discover the on-call topology around them: services, escalation policies, schedules, who is on call, users, and teams.

Run these through `omni-cli` once a human has connected the platform (`omni-cli pagerduty login`). Full parameter and output schemas come from `omni-cli discovery pagerduty`.

## escalation policies

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty escalation-policy get` | Get one escalation policy with its rules and targets. | read |
| `omni-cli pagerduty escalation-policy list` | List escalation policies with their rules and targets (who gets paged, in what order). | read |

## incidents

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty incident add-note` | Add a note to an incident, attributed to the login email via the From header. | write |
| `omni-cli pagerduty incident create` | Create (trigger) an incident on a service — attributed to the login email via the From header. Reusing an incident-key on the same service is refused with 400. | write |
| `omni-cli pagerduty incident get` | Get one incident with its assignments, acknowledgements, and pending actions. | read |
| `omni-cli pagerduty incident list` | List incidents filtered by status, service, team, user, urgency, or time window — the triage entry point. Classic pagination hard-caps at offset + limit = 10,000 (HTTP 400 beyond); narrow with statuses/since/until/service-ids instead of paging that deep. | read |
| `omni-cli pagerduty incident list-notes` | List the notes on an incident (the human timeline of the response). | read |
| `omni-cli pagerduty incident update` | Acknowledge or resolve an incident; optionally retitle, change urgency, or escalate. PagerDuty rejects a repeat of a completed transition (400 code 2001, e.g. "Incident Already Resolved") — verify current status via incident.get before retrying. | write |

## on call

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty oncall list` | List on-call entries — who is on call now (or in a window), per escalation policy, level, and schedule. | read |

## schedules

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty schedule get` | Get one schedule; pass since/until to render final_schedule entries — who actually covers that window. | read |
| `omni-cli pagerduty schedule list` | List on-call schedules (discovers schedule ids; render actual coverage with schedule.get and a window). | read |

## services

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty service get` | Get one service with its timeouts, urgency rules, support hours, and integrations. | read |
| `omni-cli pagerduty service list` | List services (discovers the service-id incident.create requires and each service's current status). | read |

## teams

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty team list` | List teams (feeds every team-ids filter). | read |

## users

| Command | What it does | Kind |
|---|---|---|
| `omni-cli pagerduty user get` | Get one user with their contact methods and notification rules. | read |
| `omni-cli pagerduty user list` | List users with their emails (discovers assignment targets and user-id filters). | read |