Linking PagerDuty as a source
This source is currently in alpha. The interface and available tables may change.
The PagerDuty connector pulls your PagerDuty incident and on-call data into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to PagerDuty.
- You need a PagerDuty REST API key. In your PagerDuty account, go to Integrations → API Access Keys and create a key, selecting the Read-only option — that's all this source needs.
- Back in PostHog, enter the key in the
API keyfield and click Next. - Select the tables you want to sync, set the sync method and frequency, then click Import.
Once the syncs are complete, you can start using PagerDuty data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
incidents | Incidents in your account | Incremental |
log_entries | Log entries recording activity on incidents | Full refresh |
services | Services that incidents are raised against | Full refresh |
users | PagerDuty users | Full refresh |
teams | Teams in your account | Full refresh |
escalation_policies | Escalation policies | Full refresh |
schedules | On-call schedules | Full refresh |
priorities | Incident priorities | Full refresh |
vendors | Integration vendors | Full refresh |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.
Sync limitations
Incremental sync on incidents filters on created_at, so it only picks up newly created incidents. Status changes to incidents created before the cursor are not re-fetched.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
incidents | An incident representing a problem on a service that requires response. | Incremental, Full refresh | created_at | — |
log_entries | A log entry recording an action or change on an incident (triggered, acknowledged, notified, etc.). | Full refresh | — | — |
services | A service representing an application, component, or team monitored in PagerDuty. | Full refresh | — | — |
users | A user account in the PagerDuty account. | Full refresh | — | — |
teams | A team that groups users, services, and escalation policies in PagerDuty. | Full refresh | — | — |
escalation_policies | An ordered set of escalation rules that determine who is notified when an incident is not handled. | Full refresh | — | — |
schedules | An on-call schedule defining which users are on call over time. | Full refresh | — | — |
priorities | A priority level that can be assigned to incidents to rank their importance. | Full refresh | — | — |
vendors | A third-party vendor that integrates with PagerDuty (e.g. a monitoring tool). | Full refresh | — | — |