Skip to main content

Notification routing

Data quality notification routing enables you to send alerts to specific Slack, Microsoft Teams, Jira, or ServiceNow channels based on asset scope, ensuring the right teams receive relevant notifications about data quality issues.

Scope types​

You can route alerts based on four asset scope types:

ScopeDescription
DatabaseRoute alerts for rules on assets within specific databases
DomainRoute alerts for rules on assets belonging to specific domains
OwnerRoute alerts for rules on assets owned by specific users or groups
TagRoute alerts for rules on assets with specific classifications

Owner and tag scopes are evaluated with the asset (table or view) where the rule is defined—not with the rule itself.

How routing works​

When a data quality rule fails, the system determines where to send the alert using a priority-based approach:

  1. Check for scoped configurations: The system looks for routing rules that match the failed asset's database, domain, owner, or tag

    • If one or more matches are found, alerts are sent to all matched configurations. For example, if a rule on a table in Database A fails, and Database A is configured to send alerts to #dq-core and #trust channels, the alert is delivered to both channels
    • Owner and tag routing works the same way: the system resolves the base asset, retrieves its owners and tags, and matches those with any owner- or tag-scoped configurations

  2. Fall back to default channel: If no scoped configuration matches the asset, alerts are sent to the default organization-level channel configured in Admin → Integrations → Data Quality

  3. Silent skip for missing properties: If an asset has no owners or no tags, routing configurations that use those scope types are silently skipped for that alert. The alert still reaches any other matching scoped configurations, or the default channel if none match

  4. Unified default setting: The same default channel setting is available from both Admin → Notifications and Admin → Integrations → Data Quality

See also​