PagerDuty
PagerDuty is a comprehensive incident management and on-call scheduling platform that enables organizations to respond to and resolve critical incidents, outages, and operational issues in real-time. It serves as a central hub for alerting, incident response, on-call management, and escalation workflows, ensuring that the right people are notified at the right time when problems occur.
| Category | On-call |
| Direction | Query source |
| Sign-in | API Token |
| Query languages | SQLite |
| Tables | 15 |
| Query templates | 49 |
| Website | pagerduty.com |
Before you start
Huntbase signs in to PagerDuty with API Token. Create the credential in PagerDuty first, then keep it to hand for the Connect step.
- To create a general access key (Admin or Account Owner), go to Integrations › Developer Tools › API Access Keys and click Create New API Key.
- Enter a description, check Read-only API Key, and click Create Key.
- If you can't create account keys, create a user token instead. Go to User Icon › My Profile › User Settings, and under API Access, click Create API User Token.
- Copy the key. This is the only time it's displayed in full.
Permissions:
- A general access key with Read-only API Key checked (limits it to
GETcalls)
For the vendor's own instructions, see PagerDuty API access keys documentation.
Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.
Connect PagerDuty
- Go to Connections and click New connection, or click New connection on the PagerDuty product page.
- On Product, pick PagerDuty and choose the Owner.
- On Details, give the connection a Name and, optionally, a Description.
- On Connect, fill in the settings and credentials described below.
- On Verify, review the summary and click Create & check.
For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.
Credentials
The only Method is API Token. Enter a Credential label (for example Production), then fill in:
| Field | Required | Notes |
|---|---|---|
| API Token | Yes | Secret — not shown again after you save it. |
Query it
Once connected, PagerDuty can serve these languages in a query tab, and Scout can use it when you ask in Auto:
| Language | Use it for |
|---|---|
| SQLite | SQL over the 15 tables listed below, alongside every other connected source. |
Example: SQLite
List all PagerDuty tags basic info — Explore which PagerDuty tags are being used.
select
id,
label,
self
from
pagerduty_tag;
PagerDuty ships with 49 query templates. Find them in Library › Queries — see Query templates.
Tables
PagerDuty adds 15 tables. Browse their columns from Schema in the query bar's ⋯ menu.
All 15 tables
| Table | Contains |
|---|---|
pagerduty_escalation_policy | An escalation policy determines what user or schedule will be notified first, second, and so on when an incident is triggered. |
pagerduty_incident | An incident represents a problem or an issue that needs to be addressed and resolved. |
pagerduty_incident_log | Records log entries for the specified incident. |
pagerduty_on_call | An on-call represents a contiguous unit of time for which a User will be on call for a given Escalation Policy and Escalation Rules. |
pagerduty_priority | A priority is a label representing the importance and impact of an incident. |
pagerduty_ruleset | Rulesets allow you to route events to an endpoint and create collections of event rules, which define sets of actions to take based on event content. |
pagerduty_ruleset_rule | An event rule allows you to set actions that should be taken on events that meet your designated rule criteria. |
pagerduty_schedule | A Schedule determines the time periods that users are On-Call. |
pagerduty_schedule_user | List users who are part of a PagerDuty schedule rotation. |
pagerduty_service | A service represents something you monitor (like a web service, email service, or database service). |
pagerduty_service_integration | A service integration is an integration that belongs to a Pagerduty service. |
pagerduty_tag | List all of your account's tags. |
pagerduty_team | Members of a PagerDuty account that have the ability to interact with incidents and other data on the account. |
pagerduty_user | Members of a PagerDuty account that have the ability to interact with incidents and other data on the account. |
pagerduty_vendor | A PagerDuty Vendor represents a specific type of integration. |
Next steps
- Connections — health, credentials and settings after you connect
- Query languages — syntax, parameters and time ranges
- Chatting with Scout — ask questions without writing a query
- All integrations — the rest of the catalog