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.

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.

Supported attributes:

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.

Further reading

추가 유용한 문서, 링크 및 기사:

Datadog On-CallDOCUMENTATION