## Configure alerts

URL: https://docs.atlan.com/product/capabilities/governance/data-quality/how-tos/configure-alerts

> Set up real-time notifications for data quality rule failures via Slack, Microsoft Teams, Jira, or ServiceNow.

Set up real-time notifications for data quality rule failures in Atlan. Receive immediate alerts via Slack, Microsoft Teams, Jira, or ServiceNow when rules fail, enabling quick response to data quality issues. This guide shows how to configure organization-level alert destinations and set rule-specific alert priorities.

## Prerequisites

Before you begin, make sure you have:
* Administrative access to Atlan (for organization-level configuration)
* Access to a public Slack or Microsoft Teams channel, a Jira project, or a ServiceNow instance
* Data quality rules already configured in your environment

## Configure organization-level alerts

Set up the alert destination for all data quality rules in your organization. This configuration applies to all rules and determines where alerts are sent. Only instance administrators can access this setting.

:::warning IMPORTANT
Only public channels are supported. Alerts can't be routed to private channels or Direct Messages at this time.
:::

1. Navigate to the **Admin** panel from the profile menu

2. In the left-hand menu, select **Integrations**

3. Choose your preferred messaging platform: **Slack** or **Microsoft Teams**

 ![Slack integration](https://docs.atlan.com/img/product-capabilities/governance/data-quality-studio/alerts-integrate-slack-channel.png)

4. Within the selected platform, scroll to the **Data Quality** section

5. Enter the name of the public channel where rule failure alerts are delivered

6. Click **Update** to activate the integration

Once saved, the alerting configuration is in effect for all data quality rules based on their priority settings.

## Configure notification routing by asset scope

Set up targeted alert routing to send data quality notifications to specific Slack, Microsoft Teams, Jira, or ServiceNow based on asset scope. This enables you to organize alerts by data ownership and guarantee the right teams receive relevant notifications. For detailed information about routing behavior and priority systems, see [Notification routing](https://docs.atlan.com/llms/governance/data-quality/notification-routing/llms.txt).

![Notification routing](https://docs.atlan.com/img/product-capabilities/governance/data-quality-studio/alerts-notification-routing-PR2.png)

### Create routing configuration

1. Navigate to the **Admin** panel from the profile menu

2. In the left-hand menu, select **Notifications**

3. Click **Add configuration** to create a new routing rule

4. Enter a descriptive **Name** for the routing configuration

5. Set the **Asset scope**:
 - Select the scope type: **Database**, **Domain**, **Owner**, or **Tag** (multi-select is supported within each scope type)
 - Choose one or more values to include in this routing rule:
 - **Database**: Route alerts for rules on assets in specific databases
 - **Domain**: Route alerts for rules on assets belonging to specific domains
 - **Owner**: Route alerts for rules on assets owned by specific users or groups
 - **Tag**: Route alerts for rules on assets with specific classifications

 :::note
 Owner and tag scopes are evaluated on the **asset** (table or view) where the rule is defined—not on the rule itself. If the asset has no owners or tags at the time a rule fails, routing by those scopes is silently skipped and the alert falls back to the default channel.
 :::

6. Configure **Send alerts to**:
 - **For Slack or Microsoft Teams**: Choose one or more public channels where alerts are delivered
 - **For Jira**:
 - Select the **Project** where rule failure tickets are created
 - Select the **Issue type** from the dropdown
 - Select the **Status** to transition to when the rule passes

 ![Jira configuration](https://docs.atlan.com/img/product-capabilities/governance/data-quality-studio/notification-config-JIRA.png)
 - **For ServiceNow**:
 - An incident is created automatically when a rule fails
 - Select the **Incident status after rule passes** to specify which status the incident transitions to when the rule passes
 - If you already use ServiceNow for Atlan data access requests, disconnect and reconnect using [Integrate ServiceNow](https://docs.atlan.com/llms/governance/integrations/integrate-servicenow/llms.txt) so that incident creation for data quality alerts is enabled.

 ![ServiceNow configuration](https://docs.atlan.com/img/product-capabilities/governance/data-quality-studio/notification-config-servicenow.png)

7. Click **Save** to activate the routing configuration

Once saved, data quality rule failures on assets within the specified scope are routed to the selected channels, create tickets in Jira, or create incidents in ServiceNow instead of the default organization-level channel.

## Configure rule-level alert priority

Set alert priorities during rule creation or editing. This determines how frequently alerts are sent for each specific rule.

![Priority levels](https://docs.atlan.com/img/product-capabilities/governance/data-quality-studio/alerts-priority-level.png)

1. Navigate to the data quality rule you want to configure

2. Open the rule for editing or create a new rule

3. In the rule creation workflow, scroll to the **Additional Settings** section

4. All rules default to Normal priority unless explicitly changed by the user. Under **Alerts**, select the desired priority level:
 * **Normal** (default): Alerts are sent up to three times per failure, then suppressed until the rule passes. Use this for most data quality rules.
 * **Urgent**: Alerts are sent every time the rule fails. Use this for critical business rules.
 * **Low**: No alerts are sent. Failures are silently logged. Use this for non-critical monitoring.

## Verify alerts

After configuration:

* Rule failures trigger alerts in the designated public Slack or Teams channel, create tickets in Jira, or create incidents in ServiceNow, based on priority
* Each alert includes full context (rule name, asset, severity, and relevant metadata) for quick triage and action
* Rule-level alert priority can be changed at any time by editing the rule

## Need help

If you have questions or need assistance with configuring alerts, reach out to Atlan Support by [submitting a support request](https://docs.atlan.com/support/submit-request).

## See also

* [Set up Databricks](https://docs.atlan.com/llms/governance/data-quality/set-up-databricks/llms.txt) - Configure Databricks for data quality monitoring
* [Set up Snowflake](https://docs.atlan.com/llms/governance/data-quality/set-up-snowflake/llms.txt) - Configure Snowflake for data quality monitoring

---