Route Alert Check Notifications

Similar to Prometheus Alertmanager, Dash0 uses labels to determine how alerts are routed to different notification channels. Labels can be attached to checks and then referenced in conditions on notification channels.

Add Labels to Checks

When configuring a check, you can add additional labels as key–value pairs. These labels will be included in the metadata of the failed check and can be used for routing.

Labels are arbitrary metadata, but they become powerful when combined with routing rules.

Define Notification Conditions

In the Notification Channels settings, you can define conditions to control which failed checks trigger notifications for a given channel.

• Each condition is built from one or more filters (for example: team = SRECopy).
• Multiple filters inside a single condition are combined with AND.
• Adding multiple conditions creates an OR between them.

This allows fine-grained control over which teams, services, or environments should receive specific alerts.

Examples:

• A condition with team = SRECopy will only notify about checks labeled with team: SRECopy.
• A channel with conditions [team = SRE] OR [team = DEV]Copy will receive notifications for both teams.

Autocompletion Behavior

When creating filters, Dash0 offers autocompletion for available keys and values. Autocompletion is based on existing failed checks:

• If no rules are currently configured, autocompletion may not suggest keys or values.
• However, conditions can still be created and will work as expected once matching failed checks occur.