Datadog Monitor
Create monitor
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Create a monitor using the specified options.
Inputs
Expand All
Logs Alert Query monitor type option.
Construct a search query using the same logic as a log explorer search, for example:
logs("@http.status_code:[500 TO 599]").index("*").rollup("count").last("20m")logs("foo").index("*").rollup("count").by("@service").last("1m")
Format: logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window).
See documentation for further formatting help.
Operator of the query. Determines whether the monitor will trigger when the evaluated value is compared using the operator to the alert threshold.
Allowed enum values: <,<=,>,>=,==,!=
critical_threshold [required]
The monitor CRITICAL threshold, also known as the alert threshold.
The monitor WARNING threshold.
List of other optional monitor thresholds available.
The monitor CRITICAL recovery threshold.
The monitor OK threshold.
The monitor UNKNOWN threshold.
The monitor WARNING recovery threshold.
Controls how groups or monitors are treated if an evaluation does not return any data points. The default option results in different behavior depending on the monitor query type. For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions. For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
Allowed enum values: default,show_no_data,show_and_notify_no_data,resolve
default: default
Whether or not to send a log sample when the log monitor triggers.
Metric Alert Query monitor type option.
Your source metric queries use the same definition language as metric graphs, for example:
avg:system.cpu.idle{*} - week_before(max:system.cpu.idle{*})max:system.disk.in_use{*} by {host} - min:system.disk.in_use{*}rate(avg:system.load.1{*}) + 1
See the graphing primer for further examples.
Format: time_aggr(time_window):space_aggr:metric{tags} [by {key}].
See documentation for further formatting help.
Operator of the query. Determines whether the monitor will trigger when the evaluated value is compared using the operator to the alert threshold.
Allowed enum values: <,<=,>,>=,==,!=
critical_threshold [required]
The monitor CRITICAL threshold, also known as the alert threshold.
The monitor WARNING threshold.
List of other optional monitor thresholds available.
The monitor CRITICAL recovery threshold.
The monitor OK threshold.
The monitor UNKNOWN threshold.
The monitor WARNING recovery threshold.
A Boolean indicating whether this monitor notifies when data stops reporting.
A message to include with notifications for this monitor. You can build a notification section in the monitor product using autocomplete and copy and paste it into this field.
Integer from 1 (high) to 5 (low) indicating alert severity.
Allowed enum values: 1,2,3,4,5
default: 5
Tags associated to your monitor.
We recommend using the is_renotify, block in the original message instead. A message to include with a re-notification. Supports the @username notification we allow elsewhere. Not applicable if Renotify interval is null.
A Boolean indicating whether notifications from this monitor automatically inserts its triggering tags into the title.
default: true
A Boolean indicating whether tagged users is notified on changes to this monitor.
The number of minutes after the last notification before a monitor re-notifies on the current status.
The number of times re-notification messages should be sent on the current status at the provided re-notification interval.
The types of monitor statuses for which re-notification messages are sent.
Outputs
Expand All
A message to include with notifications for this monitor.
Tags associated to your monitor.
A map of tags where both the keys and the values are strings. If a key has multiple values, the last value wins.
A map of tags where the keys are strings and the values are lists of strings.
List of options associated with your monitor.
Type of aggregation performed in the monitor query.
IDs of the device the Synthetics monitor is running on.
Whether or not to send a log sample when the log monitor triggers.
We recommend using the is_renotify, block in the original message instead.
default: none
Time (in seconds) to delay evaluation, as a non-negative integer.
Whether the log alert monitor triggers a single alert or multiple alerts when any group breaches a threshold.
A Boolean indicating whether notifications from this monitor automatically inserts its triggering tags into the title.
default: true
Whether or not the monitor is locked (only editable by creator and admins).
How long the test should be in failure before alerting (integer, number of seconds, max 7200).
The minimum number of locations in failure at the same time during at least one moment in the min_failure_duration period (min_location_failed and min_failure_duration are part of the advanced alerting rules - integer, >= 1).
default: 1
Time (in seconds) to skip evaluations for new groups.
Time (in seconds) to allow a host to boot and applications to fully start before starting the evaluation of monitor results.
default: 300
The number of minutes before a monitor notifies after data stops reporting.
Visibility setting for content displayed in notification.
A Boolean indicating whether tagged users is notified on changes to this monitor.
A Boolean indicating whether this monitor notifies when data stops reporting.
The number of minutes after the last notification before a monitor re-notifies on the current status.
The number of times re-notification messages should be sent on the current status at the provided re-notification interval.
The types of monitor statuses for which re-notification messages are sent.
A Boolean indicating whether this monitor needs a full window of data before it’s evaluated.
Information about the downtime applied to the monitor.
ID of the corresponding Synthetic check.
List of the different monitor threshold available.
The monitor CRITICAL threshold.
The monitor CRITICAL recovery threshold.
The monitor OK threshold.
The monitor UNKNOWN threshold.
The monitor WARNING threshold.
The monitor WARNING recovery threshold.
Alerting time window options.
The number of hours of the monitor not reporting data before it automatically resolves from a triggered state.
List of requests that can be used in the monitor query.
Data source for event platform-based queries.
An array of index names to query in the stream.
Aggregation methods for event platform queries.
Allowed enum values: count,cardinality,median,pc75,pc90,pc95,pc98,pc99,sum,min,max,avg
A time interval in milliseconds.
Measurable attribute to compute.
Options for sorting group by results.
Metric used for sorting group by results.
Aggregation methods for event platform queries.
Allowed enum values: count,cardinality,median,pc75,pc90,pc95,pc98,pc99,sum,min,max,avg
Number of groups to return.
Name of the query for use in formulas.
The different states your monitor can be in.
Allowed enum values: Alert,Ignored,No Data,OK,Skipped,Unknown,Warn
The query evaluated by the monitor
The type of the monitor.
Allowed enum values: composite,event alert,log alert,metric alert,process alert,query alert,rum alert,service check,synthetics alert,trace-analytics alert,slo alert,event-v2 alert,audit alert,ci-pipelines alert
Integer from 1 (high) to 5 (low) indicating alert severity.
Whether or not the monitor is broken down on different groups.
Timestamp of the monitor creation.
Whether or not the monitor is deleted.
Last timestamp when the monitor was edited.
Wrapper object with the different monitor states.
Dictionary where the keys are groups (comma separated lists of tags) and the values are the list of groups your monitor is broken down on.
A list of role identifiers that can be pulled from the Roles API.
Timestamp of last time the state of the monitor changed.
Unix timestamp of monitor creation.
