Manage account-level notification destinations
This feature is in Beta. To use it, an account admin must turn on Account-level Webhook Destinations from the account console Previews page. See Manage account-level previews.
Account-level notification destinations send account-level events, such as budget alerts, to external systems using webhooks. They are separate from workspace-level notification destinations, which workspace admins configure in each workspace.
You must be an account admin to manage account-level notification destinations.
Networking requirements
The receiving endpoint must meet the following requirements:
-
Databricks enforces the use of HTTPS for security. The notification destination must use Secure Sockets Layer (SSL) certificates signed by a trusted certificate authority.
-
The notification destination URL must use port 443. You can leave the port out of the URL, because HTTPS uses port 443 by default. If your endpoint listens on a different port, put a reverse proxy on port 443 in front of it.
-
The notification destination must add the control plane outbound IP addresses of the Databricks central region to its allowlist, even if your workspaces are in other regions. See IP addresses and domains for Databricks services and assets.
The central region is
us-central1.
These IP addresses are shared across Databricks accounts, so an allowlist alone doesn't confirm that a request came from your account. Configure HTTP basic authentication on the destination, and have your endpoint check the credentials and the account_id in each payload.
Create a new notification destination
To configure a new notification destination:
-
Open the notification destinations page in the account console.
Go directly to the notification destinations page, or click Settings in the account console sidebar and then click the Notifications tab.
-
Click Add destination.
-
Enter a Name and the webhook URL.
-
(Optional) Enter a Username and Password to authenticate requests with HTTP basic authentication.
-
Click Create.
Account-level notification destinations support only webhook destinations, with optional HTTP basic authentication. OAuth authentication isn't supported.
Additional resources
To send budget alerts to a destination, see Trigger custom webhooks.