PagerDuty connector reference

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure 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	id	Incidents in your PagerDuty account, including status, urgency, assignments, acknowledgements, and priority.	Incremental	created_at
log_entries	id	Log entries recording actions taken on incidents, such as triggers, acknowledgements, escalations, and resolutions.	Incremental	created_at
services	id	Services monitored in PagerDuty, including escalation policy, alert grouping, and support hours.	Full refresh only
users	id	Users in your PagerDuty account, including role, contact methods, notification rules, and team membership.	Full refresh only
teams	id	Teams in your PagerDuty account, including name, description, and default role.	Full refresh only
priorities	id	Priority levels defined for your PagerDuty account.	Full refresh only
escalation_policies	id	Escalation policies, including escalation rules, targets, and associated services and teams.	Full refresh only
schedules	id	On-call schedules, including assigned users, teams, and escalation policies.	Full refresh only
oncalls	escalation_policy_id, user_id, schedule_id, escalation_level, start	Current and scheduled on-call assignments, mapping users to escalation policies and schedules.	Full refresh only
audit_records	lw_id	Audit trail records of actions taken in your PagerDuty account, including the actor, method, and affected resource.	Incremental	execution_time

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
id	STRING
incident_number	BIGINT
title	STRING
description	STRING
created_at	TIMESTAMP
updated_at	TIMESTAMP
status	STRING
incident_key	STRING
urgency	STRING
html_url	STRING
summary	STRING
type	STRING
self	STRING
service	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
assignments	ARRAY<STRUCT<at: TIMESTAMP, assignee: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>>
assigned_via	STRING
acknowledgements	ARRAY<STRUCT<at: TIMESTAMP, acknowledger: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>>
last_status_change_at	TIMESTAMP
last_status_change_by	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
first_trigger_log_entry	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
escalation_policy	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
teams	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
priority	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING, name: STRING, color: STRING, description: STRING, order: BIGINT>
resolve_reason	STRUCT<type: STRING, incident: STRUCT<id: STRING, type: STRING, summary: STRING>>
alert_counts	STRUCT<all: BIGINT, triggered: BIGINT, resolved: BIGINT>
conference_bridge	STRUCT<conference_number: STRING, conference_url: STRING>
incidents_responders	ARRAY<STRUCT<state: STRING, user: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, incident: STRUCT<id: STRING, type: STRING, summary: STRING>, updated_at: TIMESTAMP, message: STRING, requester: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, requested_at: TIMESTAMP>>
responder_requests	ARRAY<STRUCT<requester: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, requested_at: TIMESTAMP, message: STRING, responder_request_targets: ARRAY<STRUCT<responder_request_target: STRUCT<id: STRING, type: STRING, summary: STRING, incidents_responders: ARRAY<STRING>>>>>>
subscriber_requests	ARRAY<STRUCT<subscriber: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, subscribable: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, account: STRUCT<id: STRING, type: STRING>, requester: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, requester_type: STRING, has_indirect_subscription: BOOLEAN, subscriber_type: STRING, created_at: TIMESTAMP>>
urgent_subscriber_count	BIGINT
is_mergeable	BOOLEAN
body	STRUCT<type: STRING, details: STRING>
custom_fields	ARRAY<STRUCT<id: STRING, name: STRING, type: STRING, data_type: STRING, field_type: STRING, description: STRING, display_name: STRING, value: STRING>>
external_references	ARRAY<STRUCT<id: STRING, type: STRING, external_id: STRING, external_url: STRING, sync_state: STRING, synced_via: STRING>>
resolved_at	TIMESTAMP
incident_type	STRUCT<name: STRING>
alert_grouping	STRING
basic_alert_grouping	STRING
pending_actions	ARRAY<STRUCT<type: STRING, at: TIMESTAMP>>

Note

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
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
created_at	TIMESTAMP
note	STRING
agent	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
channel	STRUCT<type: STRING, raw_event: STRING, details: STRING, cef_details: STRING>
service	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
incident	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
teams	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
contexts	ARRAY<STRUCT<type: STRING, href: STRING, text: STRING>>
event_details	STRUCT<description: STRING>
assignees	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>

services

Primary key: id Sync mode: Full refresh only

Field	Data type
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
name	STRING
description	STRING
auto_resolve_timeout	BIGINT
acknowledgement_timeout	BIGINT
created_at	TIMESTAMP
updated_at	TIMESTAMP
status	STRING
last_incident_timestamp	TIMESTAMP
escalation_policy	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
teams	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
incident_urgency_rule	STRUCT<type: STRING, urgency: STRING, during_support_hours: STRUCT<type: STRING, urgency: STRING>, outside_support_hours: STRUCT<type: STRING, urgency: STRING>>
support_hours	STRUCT<type: STRING, time_zone: STRING, start_time: STRING, end_time: STRING, days_of_week: ARRAY<INT>>
scheduled_actions	ARRAY<STRUCT<type: STRING, at: STRUCT<type: STRING, name: STRING>, to_urgency: STRING>>
addons	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
alert_creation	STRING
alert_grouping	STRING
alert_grouping_parameters	STRUCT<type: STRING, config: STRUCT<timeout: BIGINT, aggregate: STRING, fields: ARRAY<STRING>, time_window: BIGINT, recommended_time_window: BIGINT>>
alert_grouping_timeout	BIGINT
auto_pause_notifications_parameters	STRUCT<enabled: BOOLEAN, timeout: BIGINT>
response_play	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
integrations	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>

users

Primary key: id Sync mode: Full refresh only

Field	Data type
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
name	STRING
email	STRING
time_zone	STRING
color	STRING
avatar_url	STRING
billed	BOOLEAN
role	STRING
description	STRING
invitation_sent	BOOLEAN
job_title	STRING
locale	STRING
created_via_sso	BOOLEAN
teams	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
contact_methods	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
notification_rules	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
coordinated_incidents	ARRAY<STRUCT<incident_id: STRING>>
license	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING, name: STRING, description: STRING, current_value: INT, allocations_available: INT, role_group: STRING, valid_roles: ARRAY<STRING>>

teams

Primary key: id Sync mode: Full refresh only

Field	Data type
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
name	STRING
description	STRING
default_role	STRING
parent	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>

priorities

Primary key: id Sync mode: Full refresh only

Field	Data type
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
name	STRING
description	STRING
color	STRING
account_id	STRING
order	BIGINT
schema_version	INT
created_at	TIMESTAMP
updated_at	TIMESTAMP

escalation_policies

Primary key: id Sync mode: Full refresh only

Field	Data type
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
name	STRING
description	STRING
num_loops	INT
on_call_handoff_notifications	STRING
send_ochons_through_level	INT
created_at	TIMESTAMP
updated_at	TIMESTAMP
escalation_rules	ARRAY<STRUCT<id: STRING, escalation_delay_in_minutes: INT, escalation_rule_assignment_strategy: STRING, targets: ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>>>
services	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
teams	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
privilege	STRUCT<permissions: ARRAY<STRING>>

schedules

Primary key: id Sync mode: Full refresh only

Field	Data type
id	STRING
type	STRING
summary	STRING
self	STRING
html_url	STRING
name	STRING
description	STRING
time_zone	STRING
users	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
teams	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
escalation_policies	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>

oncalls

Primary key: escalation_policy_id, user_id, schedule_id, escalation_level, start Sync mode: Full refresh only

Field	Data type
escalation_policy_id	STRING
user_id	STRING
schedule_id	STRING
escalation_level	INT
start	TIMESTAMP
end	TIMESTAMP
escalation_policy	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
user	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
schedule	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>

audit_records

Primary key: lw_id Cursor field: execution_time

Field	Data type
lw_id	STRING
time	TIMESTAMP
id	STRING
self	STRING
execution_time	TIMESTAMP
execution_context	STRUCT<request_id: STRING, remote_address: STRING>
actors	ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>
method	STRUCT<description: STRING, type: STRING, truncated_token: STRING>
root_resource	STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>
action	STRING
details	STRUCT<resource: STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>, fields: ARRAY<STRUCT<name: STRING, description: STRING, value: STRING, before_value: STRING>>, references: ARRAY<STRUCT<name: STRING, description: STRING, added: ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>, removed: ARRAY<STRUCT<id: STRING, type: STRING, summary: STRING, self: STRING, html_url: STRING>>>>>

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
incidents.read	incidents, log_entries
services.read	services
users.read	users
teams.read	teams
priorities.read	priorities
escalation_policies.read	escalation_policies
schedules.read	schedules
oncalls.read	oncalls
audit_records.read	audit_records
custom_fields.read	incidents
subscribers.read	incidents