Skip to main content

Configure alerts

Set up real-time notifications for data quality rule failures in Atlan. Receive immediate alerts via Slack or Microsoft Teams 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
  • 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.

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

  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 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

  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.

Next steps​

After completing these steps:

  • Rule failures trigger alerts in the designated public Slack or Teams channel, based on priority
  • Each alert includes full context - rule name, asset, severity, and relevant metadata - to aid quick triage and action
  • Rule-level alert priority settings can be modified 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.

See also​