This feature is in Public Preview.
This article teaches you how to create and configure notification destinations for your workspace.
System notifications are messages that tell you when your workflow experiences a run event (start, success, and failure). By default, notifications are sent to user email addresses, but admins can configure alternate notification destinations using webhooks. This allows you to build event-driven integrations with Databricks.
You must be a Databricks workspace admin to manage notification destinations. After a destination is configured, it is available to all users.
To configure a new notification destination
Click your username in the top bar of the workspace and select Admin Settings from the dropdown.
Click the Notifications tab.
Click the Manage button.
Click +Add destination.
Select a destination type. The following destinations are currently supported:
Configure the destination based on the type.
The configuration of a destination is securely stored encrypted in your Databricks workspace. To improve security if the third-party endpoint is compromised, Databricks recommends using different credentials for each configured destination. These include:
Slack: the URL to which the notification is sent.
MS Teams: the URL to which the notification is sent.
PagerDuty: integration key used to uniquely route notifications to a PagerDuty service.
Webhook: username and password used to authenticate to a third party endpoint using HTTP Basic authentication when delivering notifications.
Using different secrets for each configured destination allows you to individually revoke access of individual notification destinations without impacting the operation of all other destinations in your Databricks workspace.
To set up a Slack destination, follow the instructions in Incoming webhooks for Slack. Paste the generated URL into your Databricks notification destination.
After configuring a destination, you can add the notification destination to a job. For more information, see Add email and system notifications for job events.
Users can configure up to three system destinations for each event type per job.