Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Databricks SQL alerts run queries on a schedule and notify you when a condition that you define is met against the query result. When you schedule an alert, its associated query runs and the condition is evaluated. You can also view an alert history to review the results of past evaluations.
To learn how to work with legacy alerts instead, see What are legacy alerts?.
What you can do with alerts
Alerts let you monitor any SQL query result on a schedule. Use them to track business KPIs, monitor data quality, watch cost trends, and catch operational issues across your Azure Databricks workloads. Common patterns across Azure Databricks include:
- Monitor business metrics in metric views: Reference a Unity Catalog metric view by its fully qualified name in the alert query to monitor governed business metrics. See Alert on metric views.
- Run an alert as a task in Lakeflow Jobs: Add an alert as a task so condition checks run on a pipeline trigger and downstream tasks can branch on the result. See SQL alert task for jobs.
Get started with alerts
The following pages cover the most common alert tasks, from authoring a new alert to ongoing management:
| Topic | Description |
|---|---|
| Create an alert | Walk through the alert editor end-to-end. Includes advanced settings and notification template customization. |
| Manage alerts | Find alerts on the listing page, share them, transfer ownership, and track changes with Azure Databricks Git folders. |
| Run alerts as tasks in Lakeflow Jobs | Add a Databricks SQL alert as a task in a job so condition checks run on a pipeline trigger and downstream tasks can branch on the result. |
| Alert query patterns | SQL patterns for aggregations, multicolumn conditions, and metric views. |
Differences from legacy alerts
The latest version of Databricks SQL alerts behaves differently from legacy alerts in a few key ways:
- Query reuse: An existing saved SQL query cannot be reused when creating an alert. Each alert owns its query definition, which can be authored directly in the new alert editor.
- Alert status values: Alert states are simplified and alerts no longer support the
UNKNOWNstatus from legacy alerts. Evaluations resolve toOK,TRIGGERED, orERROR.
You can continue to use both the latest alerts and legacy alerts side by side while you transition.