PagerDuty connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed PagerDuty ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which PagerDuty plans does the connector require?
The general REST API tables work on standard PagerDuty plans. The audit_records table requires a plan that includes Audit Trail Reporting: Business, Enterprise for Incident Management, or Digital Operations (legacy). See the PagerDuty Audit Trail Reporting documentation.
Which tables does the connector support?
The connector supports 10 source tables: incidents, log_entries, services, users, teams, priorities, escalation_policies, schedules, oncalls, and audit_records. For the full schemas, see Destination table schemas.
How far back can the connector ingest data?
For incremental tables, the first sync ingests records from the previous 180 days, and each later sync ingests records created after the last run. Full-refresh tables reingest all available records on every run. PagerDuty makes audit records from the last 12 months available, and the connector reads them in windows of up to 31 days.
Does the connector capture incident updates and deletions?
The incidents table captures inserts only. PagerDuty filters this table by created_at, so the connector does not reflect updates or deletions between syncs. Schedule a periodic full refresh to capture the latest incident status.
Who must create the PagerDuty OAuth app?
An account admin must create the app. Only account admins can create scoped OAuth 2.0 apps in PagerDuty. See Configure authentication to PagerDuty.
Which authentication methods does the connector support?
The connector supports OAuth machine-to-machine (M2M) authentication only. OAuth U2M and basic authentication with a username and password are not supported.
Does the connector support the PagerDuty EU region?
Yes. The connector supports both the US and EU service regions. Select your account region when you create the connection. See Create a PagerDuty connection.