Overview

Notifications are a key component of monitors that keep your team informed of issues and support troubleshooting. When creating your monitor, configure your response to:

• Craft an actionable message.
• Trigger a workflow or create a workflow from a monitor.
• Automatically create a case.
• Automatically create an incident.

Constructing effective titles and messages

This approach helps ensure your monitor titles and messages are clear, actionable, and tailored to your audience’s needs.

• Unique titles: Add a unique title to your monitor (this is required). For multi alert monitors, some tags identifying your triggering scope are automatically inserted. You can use tag variables to enhance specificity.
• Message field: The message field supports standard Markdown formatting and variables. Use conditional variables to modulate the notification text sent to different contacts with @notifications.

{{#is_alert}} <-- conditional variable

Steps to free up disk space on {{host.name}}: <-- tag variable

1. Remove unused packages
2. Clear APT cache
3. Uninstall unnecessary applications
4. Remove duplicate files

@slack-incident-response <-- channel to send notification

{{/is_alert}}

Notification recipients

Datadog recommends using monitor notification rules to manage monitor notifications. With notification rules you can automate which notification recipients are added to a monitor based on predefined sets of conditions. Create different rules to route monitor alerts based on the tags of the monitor notification so you don’t have to manually set up recipients nor notification routing logic for each individual monitor.

In both notification rules and individual monitors, you can use an @notification to add a team member, integration, workflow, or case to your notification. As you type, Datadog auto-recommends existing options in a drop-down menu. Click an option to add it to your notification. Alternatively, click @ Add Mention, Add Workflow, or Add Case.

An @notification must have a space between it and the last line character:

Workflows

You can trigger a workflow automation or create a new workflow from a monitor.

Before you add a workflow to a monitor, add a monitor trigger to the workflow.

After you add the monitor trigger, add an existing workflow to your monitor or create a new workflow. To create a new workflow from the monitors page:

1. Click Add Workflow.
2. Click the + icon and select a Blueprint, or select Start From Scratch.

For more information on building a workflow, see Build workflows.

Incidents

Incidents can be automatically created from a monitor when the monitor transitions to an alert, warn, or no data status. Click on Add Incident and select an @incident- option. Admins can create @incident- options in Incident Settings.

When an incident is created from a monitor, the incident’s field values are automatically populated based on the monitor’s tags. For example, if your monitor has a tag service:payments, the incident’s service field will be set to “payments”. To receive notifications for these incidents, make sure the monitor’s tags align with your incident notification rules. Note: Incident notification rules are configured separately from monitor notification rules and need to be set up independently. For more information, see Incident Notification.

Toggle additional content

Monitor notifications include content such as the monitor’s query, the @-mentions used, metric snapshots (for metric monitors), and links back to relevant pages in Datadog. You have the option to choose which content you would like to include or exclude from notifications for individual monitors.

The options are:

• Default: No content is hidden.
• Hide Query: Remove the monitor’s query from the notification message.
• Hide Handles: Remove the @-mentions that are used in the notification message.
• Hide All: Notification message does not include query, handles, any snapshots (for metric monitors), or additional links in footers.

Note: Depending on the integration, some content may not be displayed by default.

Renotify

Enable monitor renotification (optional) to remind your team that a problem is not solved.

Configure the renotify interval, the monitor states from which the monitor renotifies (within alert, no data, and warn) and optionally set a limit to the number of renotification messages sent.

For example, configure the monitor to stop renotifying after 1 occurrence to receive a single escalation message after the main alert. Note: Attribute and tag variables in the renotification are populated with the data available to the monitor during the time period of the renotification.

If renotification is enabled, you are given the option to include an escalation message that is sent if the monitor remains in one of the chosen states for the specified time period.

The escalation message can be added in the following ways:

• In the {{#is_renotify}} block in the original notification message (recommended).
• In the Renotification message field in the Configure notifications and automations section.
• With the escalation_message attribute in the API.

If you use the {{#is_renotify}} block, the original notification message is also included in the renotification, so:

1. Include only extra details in the {{#is_renotify}} block and don’t repeat the original message details.
2. Send the escalation message to a subset of groups.

Learn how to configure your monitors for those use cases in the example section.

Metadata

Add metadata (Priority, Tags, Datadog Team) to your monitor. Monitor Priority allows you to set the importance of your monitor through P-level (P1 to P5). Monitor tag–which are different from metric tags–are used in the UI to group and search for monitors. If tag policies are configured, the required tags and tag values need to be added. To learn more, see Tag Policies. Datadog Teams allows you to set a layer of ownership to this monitor and view all the monitors linked to your team. To learn more, see Datadog Teams.

{{#is_alert}}
{{override_priority 'P1'}}
 ...
{{/is_alert}}
{{#is_warning}}
{{override_priority 'P4'}}
...
{{/is_warning}}

Aggregation

If the monitor’s query is grouped, you can remove one or more of the dimensions from the notification grouping, or remove them all and notify as a Simple Alert.

Find more information on this feature in Configure Monitors

Test notifications

After defining your monitor, test the notifications with the Test Notifications button at the bottom right of the monitor page.

Test notifications are supported for the monitor types: host, metric, anomaly, outlier, forecast, logs, rum, apm, integration (check only), process (check only), network (check only), custom check, event, and composite.

1. From the test notifications pop-up, choose the monitor transition to test and the group (available only if the query has grouping). You can only test states that are available in the monitor’s configuration for the thresholds specified in the alerting conditions. Recovery thresholds are an exception, as Datadog sends a recovery notification once the monitor either is no longer in alert, or it has no warn conditions.

2. Click Run Test to send notifications to the people and services listed in the monitor.

Events

Test notifications produce events that can be searched within the event explorer. These notifications indicate who initiated the test in the message body with [TEST] in notification title.

Tag variables are only populated in the text of Datadog child events. The parent event only displays an aggregation summary.

Variables

Message variables auto-populate with a randomly selected group based on the scope of your monitor’s definition, for example:

{{#is_alert}}
{{host.name}} <-- will populate
{{/is_alert}}

Further Reading

Additional helpful documentation, links, and articles:

Create monitorsDOCUMENTATION Manage monitorsDOCUMENTATION Take a course to customize alert monitor notificationsLEARNING CENTER