This feature is in Public Preview. Contact your Databricks representative to request access.
Alerts notify you when a field returned by a scheduled query meets a threshold. Use alerts to monitor your business or integrate them with tools to start workflows such as user onboarding or support tickets. Alerts complement scheduled queries, but their criteria are checked after every execution.
- A query schedule is not required but is highly recommended for alerts. If you add an alert to a non-scheduled query you will be notified only if a user executes the query manually and the alert criteria are met.
- Alerts don’t work for queries with parameters.
To see a list of alerts, click Alerts in the sidebar. By default, alerts are sorted in reverse chronological order by the Created By column. You can reorder the list by clicking the column headings.
- Name shows the string name of each alert.
- Created By shows the user that created the alert.
- State shows whether the alert status is
TRIGGEREDmeans that on the most recent execution, the Value column in your target query met the Condition and Threshold you configured. If your alert checks whether “cats” is above 1500, your alert will be triggered as long as “cats” is above 1500.
OKmeans that on the most recent query execution, the Value column did not meet the Condition and Threshold you configured. This doesn’t mean that the Alert was not triggered previously. If your “cats” value is now 1470 your alert will show as OK.
UNKNOWNmeans Databricks SQL does not have enough data to evaluate the alert criteria. You will see this status immediately after creating your Alert until the query has executed. You will also see this status if there was no data in the query result or if the most recent query result doesn’t include the Value Column you configured.