Routing Rules

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Overview

With routing rules, you can define granular logic to control how alerts reach your team. Instead of sending alerts through a single escalation policy, you can create flexible, condition-based rules to route them based on priority, time of day, tags, and more.

Routing rules examples

Route alerts by priority:
- Send priority 1 alerts to your primary escalation policy.
- Send priority 2–4 alerts to Slack or Microsoft Teams.
Route alerts by time of day:
- During business hours, route alerts to an escalation policy.
- After hours, route critical alerts to paging, and non-critical alerts to chat.
Use Dynamic Urgency to automatically detect urgency from the monitor alert:
- warn status ➝ low urgency
- alert status ➝ high urgency
The urgency of a page determines how end users are notified, based on their preferences.
Trigger workflows (coming soon): Use routing rules to trigger automated workflows in response to matching alerts.

Send Pages to Slack or Microsoft Teams

A sample routing rule, which routes all incoming Pages to Slack and Microsoft Teams.

When you route Pages to Slack or Microsoft Teams, Datadog sends a notification to the configured channel and creates a corresponding Page object in the On-Call platform. From Slack, team members can use interactive buttons to acknowledge, resolve, escalate, or declare an incident. This streamlines incident response without leaving the chat environment.

When a Page is acknowledged or resolved in Slack, Datadog updates the original notification in place, without sending additional messages. This keeps responders focused by reducing noise and showing the current Page status directly in the original thread.

Routing rule syntax

Routing rules use Datadog query syntax and support multiple if/else conditions. Rules are evaluated from top to bottom, and the final rule must act as a fallback that routes all unmatched alerts to an escalation policy.

Routing rule syntax is case-sensitive. For example, `tags.env:Prod` will not match `tags.env:prod`.

Supported attributes:

Attribute	Description	Example
`tags`	Tags on the incoming alert	`tags.env:prod`
`groups`	Monitor group names	`groups:"service:checkout-service"`
`priority`	Monitor priority (1–5)	`priority:(1 OR 2)`
`alert_status`	Monitor status (`error`, `warn`, `success`)	`alert_status:(error OR warn)`

Best practices

Balance visibility with urgency:
- Use paging and escalation policies for critical alerts that require immediate action.
- Use Slack or Teams for lower-severity issues that need awareness but don’t warrant an on-call response.