Alerts for anomaly detection

This page describes how to set up and view alerts for anomaly detection. For an introduction to anomaly detection, see Anomaly detection.

Alerts notify you when anomaly detection identifies a data quality issue, such as a stale table or an unexpected drop in row count. Create and manage alerts in the following places:

• The Data Quality Monitoring results UI. See Alerts in the Data Quality Monitoring UI.
• The Data Quality Monitoring dialog on a schema's Details page, where you enable anomaly detection. See Set up schema alerts.

Both manage the same alert rules, so a change that you make in one place appears in the other.

Alerts in the Data Quality Monitoring UI

Alert rules notify the workspace users and notification destinations you select when an unhealthy table is detected within a catalog or schema. You create and manage these rules directly from the Data Quality Monitoring UI.

Each alert rule is scoped to a catalog or a specific schema. When a monitored table within the rule's scope becomes unhealthy, each recipient receives one notification per important unhealthy table, with the same summary and a link to view the results in the Data Quality Monitoring UI.

Notification destinations

In addition to notifying workspace users by email, you can send alerts to Slack, Microsoft Teams, or webhook notification destinations.

note

Notification destinations must be configured by a workspace admin. When you set up an alert, you select from the destinations that already exist in the workspace. If the destination you need isn't listed, ask a workspace admin to create one.

Required permissions

The privileges required to create or manage an alert rule depend on the rule's scope:

• To create a schema-level alert, you must have the MANAGE privilege on the schema.
• To create a catalog-level alert, you must have the MANAGE privilege on the catalog.

View and manage data quality monitoring alerts

To view your alert rules:

1. Navigate to a schema in Catalog Explorer. Data quality monitoring must be enabled for this schema.
2. Click the Details tab. Next to Data Quality Monitoring, click View results. This opens the Data Quality Monitoring UI.
3. In the upper-right corner of the page, click Manage alerts. A popover opens showing your existing alert rules, including the catalog, schema, and notify targets for each rule.

From this popover, you can create a new alert rule, select an existing alert to edit its scope and notify targets, or delete the alert.

Create an alert

To create an alert:

1. In the upper-right corner of the Data Quality Monitoring UI, click Manage alerts to open the alerts popover.

2. Click Create alert.

3. Configure the alert rule:

   • Catalog: Select the catalog to monitor.
   • Schema: Select a specific schema, or select All Schemas to create a catalog-level alert that covers every schema in the catalog.
   • Notify: Search for and select who to notify when a table becomes unhealthy:
     • Workspace users are notified by email.
     • Notification destinations send the alert to a Slack, Microsoft Teams, or webhook channel.

4. Click Save.

Set up schema alerts

You can set up a schema's alert in the Data Quality Monitoring dialog, the same dialog that you use to enable anomaly detection. The dialog edits the schema-level alert rule that Manage alerts shows for the schema. To create a catalog-level alert, use Manage alerts. See Create an alert.

You must have the privileges to create a schema-level alert. See Required permissions.

To set up an alert in the dialog:

1. Navigate to the schema in Catalog Explorer and click the Details tab.

2. Next to Data Quality Monitoring, click the pencil icon. If anomaly detection isn't enabled yet, click Enable.

3. In the Data Quality Monitoring dialog, turn on Alerts.

4. Search for and select who to notify when a table in the schema becomes unhealthy:

   • Workspace users are notified by email.
   • Notification destinations send the alert to a Slack, Microsoft Teams, or webhook channel.

   

5. Click Save.

To stop alerts for the schema, turn off Alerts and click Save. This deletes the schema's alert rule.