pagerduty

PagerDuty - Printing Press CLI

Prerequisites: Install the CLI

This skill drives the pagerduty-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install pagerduty --cli-only
   

2. Verify: pagerduty-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/monitoring/pagerduty/cmd/pagerduty-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Triage the incident queue, resolve who's on call now and next, and run service and escalation hygiene checks without leaving the shell. Sync once and the local store powers analytics no single API call exposes: pulse for what's hot right now, oncall who for the live escalation chain, audit coverage for escalation gaps, and insights mttr/responders/noisy for offline post-incident analytics.

When to Use This CLI

Choose this CLI when an agent or operator needs to manage PagerDuty incidents, on-call schedules, services and escalation policies from the terminal, or when they need cross-entity analytics (MTTA/MTTR, on-call coverage, responder workload, noisy services) that the live API exposes only through the paid Analytics product or not at all. It is the right tool for MSP NOC triage, on-call resolution under pressure, and monthly reliability reviews.

Anti-triggers

Do not use this CLI for:

• Do not use this CLI to send or ingest events/alerts (triggering incidents from monitoring) - that is the PagerDuty Events API v2, a separate ingestion surface this CLI does not wrap.
• Do not use it for real-time push notifications or webhook delivery - it polls REST; use PagerDuty webhook subscriptions for push.
• Do not treat insights mttr/responders/noisy as a replacement for paid PagerDuty Analytics in billing disputes - they are offline reconstructions from synced log entries and only as complete as the last sync window.
• Do not use it to administer users/SSO/billing at the account level - account provisioning belongs in the PagerDuty web admin console.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Local-store analytics that compounds

• pulse - One offline call shows what's hot right now: open incidents bucketed by service, urgency and status with how long each has gone unacknowledged, sorted by SLA risk.

  Reach for this instead of N web-UI tabs when an agent or NOC analyst needs the current incident picture across every service in one shot.

  pagerduty-cli pulse --agent
  

• audit coverage - Flags services whose escalation chain is broken: empty tiers, single point of failure, expired or empty schedules, or no escalation policy at all.

  Run before an on-call rotation to catch services that would page nobody when they break.

  pagerduty-cli audit coverage --agent
  

• insights mttr - Mean time to acknowledge and resolve, computed from synced log-entry timestamps and grouped by service, team or priority.

  Use for post-incident reviews to get MTTA/MTTR by service this month without scripting the analytics API.

  pagerduty-cli insights mttr --by service --since 30d --agent
  

• insights responders - Per-responder page, ack and resolve counts plus the share of pages that landed off-hours (nights and weekends).

  Reach for this for on-call fairness and burnout reviews to see who is carrying the off-hours load.

  pagerduty-cli insights responders --since 30d --agent
  

• insights noisy - Ranks services by incident volume, auto-resolve rate and re-trigger/flapping rate over a window.

  Use to find which services to tune first when alert fatigue is high.

  pagerduty-cli insights noisy --top 10 --since 7d --agent
  

• incidents changes - For an incident, see the change events that shipped on the same service in the window right before it triggered, ranked by proximity.

  Reach for this first in root-cause triage: it answers 'what shipped right before this broke' without opening the web UI.

  pagerduty-cli incidents changes PT4KHLK --window 120m --agent
  

• audit schedule-gaps - Find future time windows where a schedule has nobody on call, before an incident finds the hole for you.

  Run before each rotation change to catch uncovered windows; neither the API nor the web UI has an equivalent report.

  pagerduty-cli audit schedule-gaps --days 14 --agent
  

• insights stale - Open incidents with no log activity past a threshold, grouped by responder and service - the ones quietly rotting.

  Use during shift handoffs to sweep forgotten incidents that pulse's SLA-risk ranking may not surface.

  pagerduty-cli insights stale --hours 24 --agent
  

On-call intelligence

• oncall who - Resolves who is on call right now for a service or team, who is on next, and the exact handoff timestamp.

  Use at 2am to know exactly who to escalate to and when the current responder hands off, without clicking through the UI.

  pagerduty-cli oncall who --service PXXXXXX --agent
  

• oncall hours - On-call hours per user over a time window, derived from synced schedule layers and overrides.

  Reach for this for monthly on-call fairness or MSP billing reviews without the paid analytics product.

  pagerduty-cli oncall hours --since 30d --agent
  

• incidents timeline - Reconstructs one incident's full chronology - trigger, every ack, note, reassignment, escalation and resolve - with elapsed deltas between events.

  Use during or after an incident to get a clean, ordered story of what happened and how long each step took.

  pagerduty-cli incidents timeline PXXXXXX --agent
  

Command Reference

abilities - This describes your account's abilities by feature name. For example "teams". An ability may be available to your account based on things like your pricing plan or account state.

• pagerduty-cli abilities get-ability - Test whether your account has a given ability. 'Abilities' describes your account's capabilities by feature name.
• pagerduty-cli abilities list - List all of your account's abilities, by name. 'Abilities' describes your account's capabilities by feature name.

addons - Manage addons

• pagerduty-cli addons create - Install an Add-on for your account.
• pagerduty-cli addons delete - Remove an existing Add-on.
• pagerduty-cli addons get - Get details about an existing Add-on.
• pagerduty-cli addons list - List all of the Add-ons installed on your account.
• pagerduty-cli addons update - Update an existing Add-on.

alert-grouping-settings - Alert Grouping Settings allow you to configure how alerts in services are grouped together into incidents.

• pagerduty-cli alert-grouping-settings delete - Delete an existing Alert Grouping Setting.
• pagerduty-cli alert-grouping-settings get - Get an existing Alert Grouping Setting.
• pagerduty-cli alert-grouping-settings list - List all of your alert grouping settings including both single service settings and global content based settings.
• pagerduty-cli alert-grouping-settings post - Create a new Alert Grouping Setting.
• pagerduty-cli alert-grouping-settings put - Update an Alert Grouping Setting.

audit - Provides audit record data.

• pagerduty-cli audit - List audit trail records matching provided query params or default criteria.

automation-actions - Automation Actions invoke jobs that are staged in Runbook Automation or Process Automation.

• pagerduty-cli automation-actions create - Create a Script, Process Automation, or Runbook Automation action
• pagerduty-cli automation-actions create-invocation - Create an Invocation
• pagerduty-cli automation-actions create-runner - Create a Process Automation or a Runbook Automation runner.
• pagerduty-cli automation-actions create-runner-team-association - Associate a runner with a team
• pagerduty-cli automation-actions create-service-assocation - Associate an Automation Action with a service
• pagerduty-cli automation-actions create-team-association - Associate an Automation Action with a team
• pagerduty-cli automation-actions delete - Delete an Automation Action
• pagerduty-cli automation-actions delete-runner - Delete an Automation Action runner
• pagerduty-cli automation-actions delete-runner-team-association - Disassociates a runner from a team
• pagerduty-cli automation-actions delete-service-association - Disassociate an Automation Action from a service
• pagerduty-cli automation-actions delete-team-association - Disassociate an Automation Action from a team
• pagerduty-cli automation-actions get - Get an Automation Action
• pagerduty-cli automation-actions get-action-service-association - Gets the details of a Automation Action / service relation
• pagerduty-cli automation-actions get-action-service-associations - Gets all service references associated with an Automation Action
• pagerduty-cli automation-actions get-action-team-association - Gets the details of an Automation Action / team relation
• `pagerduty-c

---

Content truncated.