PagerDuty connector reference
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page has reference information for the managed PagerDuty connector, including supported source tables and destination table schemas.
Supported source tables
The PagerDuty connector supports the following source tables, all under the default source schema:
Source table | Primary key | Description | Sync mode | Cursor field |
|---|---|---|---|---|
|
| Incidents in your PagerDuty account, including status, urgency, assignments, acknowledgements, and priority. | Incremental |
|
|
| Log entries recording actions taken on incidents, such as triggers, acknowledgements, escalations, and resolutions. | Incremental |
|
|
| Services monitored in PagerDuty, including escalation policy, alert grouping, and support hours. | Full refresh only | |
|
| Users in your PagerDuty account, including role, contact methods, notification rules, and team membership. | Full refresh only | |
|
| Teams in your PagerDuty account, including name, description, and default role. | Full refresh only | |
|
| Priority levels defined for your PagerDuty account. | Full refresh only | |
|
| Escalation policies, including escalation rules, targets, and associated services and teams. | Full refresh only | |
|
| On-call schedules, including assigned users, teams, and escalation policies. | Full refresh only | |
|
| Current and scheduled on-call assignments, mapping users to escalation policies and schedules. | Full refresh only | |
|
| Audit trail records of actions taken in your PagerDuty account, including the actor, method, and affected resource. | Incremental |
|
The audit_records destination table is liquid clustered on the time column for efficient time-range queries.
Connector options
The PagerDuty connector has no additional configuration options beyond the pipeline settings available for all managed connectors. See Ingest data from PagerDuty.
Destination table schemas
incidents
Primary key: id
Cursor field: created_at
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The incidents table captures inserts only. PagerDuty filters this table by created_at, so incident updates and deletions require a periodic full refresh. See PagerDuty connector limitations.
log_entries
Primary key: id
Cursor field: created_at
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
services
Primary key: id
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
users
Primary key: id
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
teams
Primary key: id
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
priorities
Primary key: id
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
escalation_policies
Primary key: id
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
schedules
Primary key: id
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
oncalls
Primary key: escalation_policy_id, user_id, schedule_id, escalation_level, start
Sync mode: Full refresh only
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
audit_records
Primary key: lw_id
Cursor field: execution_time
Field | Data type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Required OAuth permissions
The PagerDuty OAuth app must grant the following read scopes. The set of scopes the connector requires depends on which tables you ingest. For more information, see the PagerDuty OAuth scopes reference.
Permission | Required for |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|