PagerDuty
Inventory PagerDuty users, roles and licenses, who can be reached and who cannot, teams, on-call schedules and escalation policies, which services have nobody to page, every tool that sends PagerDuty alerts and every place PagerDuty sends incident data, apps users have authorized, and the Audit Trail of who changed what.
Questions you can answer 18
Each one is a saved query that ships with ConfigView, reading your PagerDuty data on your own server. Ask it in plain English, SQL, Slack or the API.
- Who are the admins in PagerDuty?
- Who can change on-call schedules and escalation policies?
- Which PagerDuty admins did not sign in through SSO?
- What changed in PagerDuty in the last 30 days?
- Who changed on-call schedules or escalation policies recently?
- Which PagerDuty changes were made through an API key?
- Which tools send alerts into PagerDuty?
- What can open incidents in PagerDuty?
- List PagerDuty integrations by vendor
- Where does PagerDuty send incident data?
- Which webhooks and extensions does PagerDuty post to?
- What outside tools are connected to PagerDuty incident workflows?
- Which PagerDuty services would page nobody?
- Are there services whose escalation policy points at an empty schedule?
- Find PagerDuty services with no reachable on-call
- Which on-call engineers would not get paged?
- Who is on call in PagerDuty but has no phone or push notifications set up?
- Are there PagerDuty responders with no notification rules?
No PagerDuty questions match that yet. Try a shorter word.
What ConfigView collects from PagerDuty 13
-
Account Features
The features the PagerDuty account's plan turns on (teams, SSO, audit trail, advanced permissions and so on), one row per feature.
-
Audit Trail
Who changed what in PagerDuty: each change to a user, team, schedule, escalation policy or service, who made it, through which API key or app, from which IP, and the names of the fields changed (not their values). Kept as a growing history. Needs a plan with Audit Trail.
-
Escalation Policies
Escalation policies: which services use each one, and at each level who gets paged (a person or a schedule) and how many minutes before it moves on.
-
Service Extensions
Extensions attached to services that send incident data out of PagerDuty (Slack, ServiceNow, Jira, generic webhooks): the kind, the host it posts to, which services use it and whether PagerDuty has disabled it after failures. No configuration or credentials are stored.
-
Licenses
The PagerDuty licenses the account has bought, how many of each are in use and free, and which user holds which license since when.
-
Connected Apps per User
Apps each user has signed in to or authorized against PagerDuty (web, mobile and third-party integrations): the app's client id, the permissions granted, and when the grant was made and expires. Only grants still in force.
-
Who Is On Call
Who is on call right now for each escalation policy and level, from which schedule, and until when.
-
On-Call Schedules
On-call schedules: time zone, which escalation policies use each one, and every person in its rotation.
-
Services
PagerDuty services: status, owning team, the escalation policy that pages people for it, when it last had an incident, and every tool that sends it alerts (Datadog, CloudWatch, email, Events API and so on). Integration keys and inbound email addresses are not stored.
-
Teams
PagerDuty teams, whether each is private or open to the rest of the account, and who belongs to each team with their team role (manager, responder, observer).
-
Users
Every PagerDuty user: name, email, role (owner, admin, user, observer, stakeholder), teams, whether they came in through SSO or are still only invited, and how many ways PagerDuty can reach them (email, phone, SMS, push) and notification rules they have. The phone numbers and addresses themselves are not stored.
-
Webhook Subscriptions
Webhook subscriptions that push incident events out of PagerDuty: the host they post to, whether they cover the whole account, one team or one service, which events they send and whether they are active. Signing secrets and header values are not stored.
-
Workflow Connections
Accounts in outside tools that PagerDuty Incident Workflows are connected to (Microsoft Teams, Jira, ServiceNow, Zoom and others): the tool, the host, the permissions granted, who set it up and whether it is healthy. Secrets are never returned.