To start configuring the monitor, complete the following:
- Define the search query: Construct a query to count events, measure metrics, group by one or several dimensions, etc.
- Set alert conditions: Define alert and warning thresholds , evaluation time frames, and configure advanced alert options.
- Say what’s happening: Write a custom notification title and message with variables.
- Notify your team: Choose how notifications are sent to your teams (email, Slack, PagerDuty, etc)
Define the search query
To learn how to construct the search query, see the individual monitor types pages. As you define the search query, the preview graph above the search fields updates.
Set alert conditions
The alert conditions vary based on the monitor type. Configure monitors to trigger if the query value crosses a threshold, or if a certain number of consecutive checks failed.
- Trigger when the
sum of the metric is
above or equal to,
below or equal to the threshold
- during the last
1 hour, or
custom to set a value between 1 minute and 48 hours (1 month for metric monitors)
The query returns a series of points, but a single value is needed to compare to the threshold. The monitor must reduce the data in the evaluation window to a single value.
|average||The series is averaged to produce a single value that is checked against the threshold. It adds the |
avg() function to your monitor query.
|max||If any single value in the generated series crosses the threshold, then an alert is triggered. It adds the |
max() function to your monitor query.*
|min||If all points in the evaluation window for your query cross the threshold, then an alert is triggered. It adds the |
min() function to your monitor query.*
|sum||If the summation of every point in the series crosses the threshold, then an alert is triggered. It adds the |
sum() function to your monitor query.
* These descriptions of max and min assume that the monitor alerts when the metric goes above the threshold. For monitors that alert when below the threshold, the max and min behavior is reversed.
Note: There are different behaviors when utilizing
as_count(). See as_count() in Monitor Evaluations for details.
A monitor can be evaluated using cumulative time windows or rolling time windows. Cumulative time windows are best suited for questions that require historical context, such as “What’s the sum of all the data available up to this point in time?” Rolling time windows are best suited for answering questions that do not require this context, such as “What’s the average of the last N data points?”
The figure below illustrates the difference between cumulative and rolling time windows.
Rolling time windows
A rolling time window has a fixed size and moves its starting point over time. Monitors support looking back at the last
1 hour, or over a custom specified time window.
Cumulative time windows
A cumulative time window has a fixed starting point and expands over time. Monitors support three different cumulative time windows:
Current hour: A time window with a maximum of one hour starting at a configurable minute of an hour. For example, monitor amount of calls an HTTP endpoint receives in one hour starting at minute 0.
Current day: A time window with a maximum of 24 hours starting at a configurable hour and minute of a day. For example, monitor a daily log index quota by using the
current day time window and letting it start at 2:00pm UTC.
Current month: Looks back at the current month starting on the first of the month at midnight UTC. This option represents a month-to-date time window and is only available for metric monitors.
A cumulative time window is reset after its maximum time span is reached. For example, a cumulative time window looking at the
current month resets itself on the first of each month at midnight UTC. Alternatively, a cumulative time window of
current hour, which starts at minute 30, resets itself every hour. For example, at 6:30am, 7:30am, 8:30am.
The evaluation frequency defines how often Datadog performs the monitor query. For most configurations, the evaluation frequency is
1 minute, which means that every minute, the monitor queries the selected data over the selected evaluation window and compares the aggregated value against the defined thresholds.
By default, evaluation frequencies depend on the evaluation window that is used. A longer window results in lower evaluation frequencies. The following table illustrates how the evaluation frequency is controlled by larger time windows:
|Evaluation Window Ranges||Evaluation Frequency|
|window < 24 hours||1 minute|
|24 hours <= window < 48 hours||10 minutes|
|window >= 48 hours||30 minutes|
The evaluation frequency can also be configured so that the alerting condition of the monitor is checked on a daily, weekly, or monthly basis. In this configuration, the evaluation frequency is no longer dependent on the evaluation window, but on the configured schedule.
For more information, see the guide on how to Customize monitor evaluation frequencies.
Use thresholds to set a numeric value for triggering an alert. Depending on your chosen metric, the editor displays the unit used (
Datadog has two types of notifications (alert and warning). Monitors recover automatically based on the alert or warning threshold but additional conditions can be specified. For additional information on recovery thresholds, see What are recovery thresholds?. For example, if a monitor alerts when the metric is above
3 and recovery thresholds are not specified, the monitor recovers once the metric value goes back below
|Alert threshold (required)||The value used to trigger an alert notification.|
|Warning threshold||The value used to trigger a warning notification.|
|Alert recovery threshold||An optional threshold to indicate an additional condition for alert recovery.|
|Warning recovery threshold||An optional threshold to indicate an additional condition for warning recovery.|
As you change a threshold, the preview graph in the editor displays a marker showing the cutoff point.
Note: When entering decimal values for thresholds, if your value is
<1, add a leading
0 to the number. For example, use
A check alert tracks consecutive statuses submitted per check grouping and compares it to your thresholds. Set up the check alert to:
Trigger the alert after selected consecutive failures:
Each check run submits a single status of
CRITICAL. Choose how many consecutive runs with the
CRITICAL status trigger a notification. For example, your process might have a single blip where connection fails. If you set this value to
> 1, the blip is ignored but a problem with more than one consecutive failure triggers a notification.
Resolve the alert after selected consecutive successes:
Choose how many consecutive runs with the
OK status resolves the alert.
See the documentation for process check, integration check, and custom check monitors for more information on configuring check alerts.
Advanced alert conditions
Notifications for missing data are useful if you expect a metric to always be reporting data under normal circumstances. For example, if a host with the Agent must be up continuously, you can expect the
system.cpu.idle metric to always report data.
In this case, you should enable notifications for missing data. The sections below explain how to accomplish this with each option.
Note: The monitor must be able to evaluate data before alerting on missing data. For example, if you create a monitor for
service:abc and data from that
service is not reporting, the monitor does not send alerts.
There are two ways to deal with missing data:
- Metric-based monitors using the limited
Notify no data option
On missing data option is supported by APM Trace Analytics, Audit Logs, CI Pipelines, Error Tracking, Events, Logs, and RUM monitors
Do not notify if data is missing or
Notify if data is missing for more than
You are notified if data is missing or if data is not missing. The notification occurs when no data was received during the configured time window.
Note: It is recommended that you set the missing data window to at least two times the evaluation period.
If you are monitoring a metric over an auto-scaling group of hosts that stops and starts automatically, notifying for no data produces a lot of notifications.
In this case, you should not enable notifications for missing data. This option does not work if it is enabled at a time when data has not been reporting for a long period.
For a monitor that does not notify on missing data, the monitor skips evaluations and stays green until data returns that would change the status from OK.
For a monitor that does not notify on missing data, if a group does not report data, the monitor skips evaluations and eventually drops the group. During this period, the bar in the results page stays green. When there is data and groups start reporting again, the green bar shows an OK status and backfills to make it look like there was no interruption.
If data is missing for
N minutes, select an option from the dropdown menu:
Evaluate as zero /
Show last known status
Show NO DATA
Show NO DATA and notify
The selected behavior is applied when a monitor’s query does not return any data. Contrary to the
Do not notify option, the missing data window is not configurable.
|Option||Monitor status & notification|
Evaluate as zero
|Empty result is replaced with zero and is compared to the alert/warning thresholds. For example, if the alert threshold is set to |
> 10, a zero would not trigger that condition, and the monitor status is set to
Show last known status
|The last known status of the group or monitor is set.|
Show NO DATA
|Monitor status is set to |
Show NO DATA and notify
|Monitor status is set to |
NO DATA and a notification is sent out.
|Monitor is resolved and status is set to |
Evaluate as zero and
Show last known status options are displayed based on the query type:
- Evaluate as zero: This option is available for monitors using
Count queries without the
- Show last known status: This option is available for monitors using any other query type than
Count, for example
Distribution, as well as for
Count queries with
After 1 hour,
After 2 hours, etc. automatically resolve this event from a triggered state.
Auto-resolve works when data is no longer being submitted. Monitors do not auto-resolve from an ALERT or WARN state if data is still reporting. If data is still being submitted, the renotify feature can be utilized to let your team know when an issue is not resolved.
For some metrics that report periodically, it may make sense for triggered alerts to auto-resolve after a certain time period. For example, if you have a counter that reports only when an error is logged, the alert never resolves because the metric never reports
0 as the number of errors. In this case, set your alert to resolve after a certain time of inactivity on the metric. Note: If a monitor auto-resolves and the value of the query does not meet the recovery threshold at the next evaluation, the monitor triggers an alert again.
In most cases this setting is not useful because you only want an alert to resolve once it is actually fixed. So, in general, it makes sense to leave this as
[Never] so alerts only resolve when the metric is above or below the set threshold.
Group retention time
You can drop the group from the monitor status after
N hours of missing data. The maximum length of time is 72 hours.
Similar to the Auto-resolve option, the group retention works when data is no longer being submitted. This option controls how long the group is kept in the monitor’s status once data stops reporting. By default, a group keeps the status for 24 hours before it is dropped. The start time of the group retention and the Auto-resolve option are identical as soon as the monitor query returns no data.
Some use cases to define a group retention time include:
- When you would like to drop the group immediately or shortly after data stops reporting
- When you would like to keep the group in the status for as long as you usually take for troubleshooting
Note: The group retention time option requires a multi alert monitor that supports the
On missing data option. These monitor types are APM Trace Analytics, Audit Logs, CI Pipelines, Error Tracking, Events, Logs, and RUM monitors.
New group delay
Delay the evaluation start by
N seconds for new groups.
The time (in seconds) to wait before starting alerting, to allow newly created groups to boot and applications to fully start. This should be a non-negative integer.
For example, if you are using containerized architecture, setting a group delay prevents monitor groups scoped on containers from triggering due to high resource usage or high latency when a new container is created. The delay is applied to every new group (which has not been seen in the last 24 hours) and defaults to
The option is available with multi alert mode.
Datadog recommends a 15-minute delay for cloud metrics, which are backfilled by service providers. Additionally, when using a division formula, a 60-second delay is helpful to ensure your monitor evaluates on complete values. See the Cloud Metric Delay
page for estimated delay times.
Delay evaluation by
The time (in seconds) to delay evaluation. This should be a non-negative integer. So, if the delay is set to 900 seconds (15 minutes), the monitor evaluation is during the last
5 minutes, and the time is 7:00, the monitor evaluates data from 6:40 to 6:45. The maximum configurable evaluation delay is 86400 seconds (24 hours).
Notify your team
Configure your notification messages to include the information you are most interested in. Specify which teams to send these alerts to as well as which attributes to trigger alerts for.
Use this section to configure notifications to your team and configure how to send these alerts:
For more information on the configuration options for the notification message, see Alerting Notifications.
Alerts are grouped automatically based on your selection of the
group by step when defining your query. If the query has no grouping, it defaults to
Simple Alert. If the query is grouped by any dimension, grouping changes to
Simple Alert mode triggers a notification by aggregating over all reporting sources. You receive one alert when the aggregated value meets the set conditions. For example, you might set up a monitor to notify you if the average CPU usage of all servers exceeds a certain threshold. If that threshold is met, you’ll receive a single notification, regardless of the number of individual servers that met the threshold. This can be useful for monitoring broad system trends or behaviors.
Multi Alert monitor triggers individual notifications for each entity in a monitor that meets the alert threshold.
For example, when setting up a monitor to notify you if the P99 latency, aggregated by service, exceeds a certain threshold, you would receive a separate alert for each individual service whose P99 latency exceeded the alert threshold. This can be useful for identifying and addressing specific instances of system or application issues. It allows you to track problems on a more granular level.
When monitoring a large group of entities, multi alerts can lead to noisy monitors. To mitigate this, customize which dimensions trigger alerts. This reduces the noise and allows you to focus on the alerts that matter most. For instance, you are monitoring the average CPU usage of all your hosts. If you group your query by
host but only want alerts to be sent once for each
service attribute meeting the threshold, remove the
host attribute from your multi alert options and reduce the number of notifications that are sent.
When aggregating notifications in
Multi Alert mode, the dimensions that are not aggregated on become
Sub Groups in the UI.
Note: If your metric is only reporting by
host with no
service tag, it is not detected by the monitor. Metrics with both
service tags are detected by the monitor.
If you configure tags or dimensions in your query, these values are available for every group evaluated in the multi alert to dynamically fill in notifications with useful context. See Attribute and tag variables to learn how to reference tag values in the notification message.
|Group by||Simple alert mode||Multi alert mode|
|(everything)||One single group triggering one notification||N/A|
|1 or more dimensions||One notification if one or more groups meet the alert conditions||One notification per group meeting the alert conditions|
- Use the Tags dropdown to associate tags with your monitor.
- Use the Teams dropdown to associate teams with your monitor.
- Choose a Priority.
Additional helpful documentation, links, and articles: