PagerDuty connector
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for PagerDuty from the Previews page. See Manage Databricks previews.
The managed PagerDuty connector in Lakeflow Connect ingests incident, on-call, service, and audit data from PagerDuty into Databricks.
Feature availability
Feature | Availability |
|---|---|
UI-based pipeline authoring |
|
API-based pipeline authoring |
|
Declarative Automation Bundles |
|
Incremental ingestion |
|
Unity Catalog governance |
|
Orchestration using Databricks Workflows |
|
API-based column selection and deselection |
|
API-based row filtering |
|
SCD Type 2 |
|
Automated schema evolution: New and deleted columns |
|
Automated schema evolution: Data type changes |
|
Automated schema evolution: Column renames |
Requires a full refresh. |
Authentication methods
Authentication method | Availability |
|---|---|
OAuth U2M |
|
OAuth M2M |
|
Basic authentication (username/password) |
|
Ingest from PagerDuty in 3 steps
Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.
- Configure PagerDuty for ingestion (Admins): Set up PagerDuty to authenticate with Databricks.
- Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Databricks to authenticate with PagerDuty.
- Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.