Configure authentication to PagerDuty

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page shows how to configure PagerDuty to enable authentication from Databricks for the PagerDuty connector. Use the credentials retrieved from the steps on this page to create a Unity Catalog connection in Databricks.

Prerequisites

• You must sign in to PagerDuty as an account admin. Only account admins can create scoped OAuth 2.0 apps. See the PagerDuty scoped OAuth documentation.
• To ingest the audit_records table, your account must be on a plan that includes Audit Trail Reporting: Business, Enterprise for Incident Management, or Digital Operations (legacy). See the PagerDuty Audit Trail Reporting documentation.

Configure PagerDuty

Register a scoped OAuth 2.0 app in PagerDuty to obtain the client credentials that Databricks uses to authenticate. For more information, see the PagerDuty app registration documentation.

1. Sign in to PagerDuty as an account admin.
2. Click Integrations, then select Developer Tools > App Registration.
3. Click New App.
4. Enter a Name and Description for the app.
5. Under Functionality, select OAuth 2.0.
6. For the OAuth 2.0 configuration, select Scoped OAuth.
7. Grant the Read scope for each resource the connector ingests: Incidents, Services, Users, Teams, Priorities, Escalation Policies, Schedules, On-Calls, Audit Records, Custom Fields, and Subscribers.
8. Click Register App.
9. Copy the Client ID and Client Secret. PagerDuty shows the client secret only once.
10. Note your account region (us or eu) and the subdomain in your PagerDuty URL. For example, for https://example-acct.pagerduty.com the subdomain is example-acct.

Next steps

Create a PagerDuty connection in Databricks. See Create a PagerDuty connection.