New feature
Beta
PagerDuty connector
PagerDuty connector is a Databricks data engineering capability, introduced August 2026.
The managed Lakeflow Connect connector that ingests PagerDuty incident, on-call, service and audit data into Databricks.
- The incidents table captures inserts only - PagerDuty filters it by created_at, so an incident resolved after it landed stays unresolved in Databricks until a full refresh.
- The oncalls table is a snapshot of who was on call at each sync, so "who was paged at 3am last Tuesday" is history you have to keep yourself.
Limitations: Incidents capture inserts only (no updates or deletes between syncs), and services, users, teams, priorities, escalation policies, schedules and oncalls reload in full on every sync. Authentication is OAuth M2M only. General SaaS connector limits apply: no automatic backfill for newly selected columns, renamed tables make the pipeline API-only, and deleted source tables are not dropped downstream.
Open in REbricked →- Category
- Data engineering
- Also known as
- PagerDuty, Lakeflow Connect for PagerDuty
- Verified
- 2026-10-20