Join the Preview!
Monitor Notification Rules are in Preview.
Overview
Monitor notification rules are predefined sets of conditions that automate the process of alerting your team based on predefined conditions and tags. Instead of individually configuring notification recipients and routing for every monitor, notification rules allow you to define the notification logic and recipients in one place and automatically route all monitor events with matching tags to that list of handles.
Creating notification rules
- Navigate to Monitors > Settings > Notification Rules.
- Click New Rule.
- Add specific tags and values to set the scope for the rule. Notification rules use an AND logic for multiple tags. For an example of this, see Routing logic.
- Add up to 50 notification recipients. Notifications can be sent to emails, Team channels, or Integration channels. For more information, see Notifications.
- Add a name for the rule.
- Click Create Rule.
Managing notification rules
From Monitor Settings
The Monitor Notification Rules page displays a table of all your notification rules with the following columns:
- Name: Notification rule name
- Scope: Shows the tag combinations that define when this rule applies (for example,
team:shopist service:web-store env:prod
). - Team: Lists the teams that this notification rule is associated with (available only when the team tag is added in the scope)
- Coverage: Shows the number of monitors that match this rule’s scopes. Use this to verify rule coverage and identify rules that need adjustment.
- Notifies: Lists the notification channels (such as Slack or email) that will receive alerts when this rule matches.
Additionally, you can click the vertical three-dot menu on the notification rule to Edit or Delete.
From an individual monitor
In your monitor configuration, you can view the notification recipients that are applied to the monitor under Recipient Summary. Notification rules automatically add recipients to monitors that match the configured scopes.
Routing logic
Notification rules apply to recipients of all monitor notifications that match the scopes defined in the rule configuration.
- Multiple tags apply an AND logic to the scope.
- Multiple rules can match a single monitor notification, and all recipients are added to the monitor alert without duplication.
The following table demonstrates how monitors with different tag combinations match notification rules and their resulting notifications. This table shows how:
- Multiple notification rules can match a single monitor notification based on its tags.
- The AND logic works for multiple tags within a rule.
- All matching notification rules contribute their recipients to the final notification list.
- Recipients are deduplicated in the final notification list.
| Notification Rules | |
---|
| team:shopist, service:web-store | team:shopist | service:web-store | service:web-store env:prod | service:web-store env:dev | |
---|
MONITOR ALERT TAGS AND NOTIFICATIONS | @slack-channel1 @jira-project | @jira-project | @jira-project | @user@datadoghq.com | @jira-project | NOTIFIED HANDLES |
team:shopist, service:web-store @user@datadoghq.com | | | | | | @slack-channel1 @jira-project @user@datadoghq.com |
team:shopist | | | | | | @jira-project |
service:web-store | | | | | | @jira-project |
service:web-store, env:prod | | | | | | @jira-project @user@datadoghq.com |
service:web-store, env:dev | | | | | | @jira-project |
team:shopist and service:web-store, env:prod @slack-service1 @jira-project @user@datadoghq.com | | | | | | @pagerduty-service1 @slack-service1 @jira-project @user@datadoghq.com |
Further reading
Additional helpful documentation, links, and articles: