After creating your monitor, use the monitor status page to view the status over time.
The page sections are expanded by default. All sections (except the header) can be closed by using the toggle (∨) icon to the left of each section name.
The header contains the monitor’s status, time of status, and monitor title. On the right are the Mute, Resolve, and settings cog buttons.
Use the mute button to mute the entire monitor or partially mute it by setting a Scope. The available scopes are based on the monitor’s group tags. See Downtimes for details on muting multiple scopes or monitors at the same time.
Note: Muting or unmuting a monitor with the UI deletes all scheduled downtimes associated with that monitor.
If your monitor is in an alert state, the Resolve button is visible. Use this button to resolve your monitor manually.
resolve function is artificially switching the monitor status to
OK for its next evaluation. The next monitor evaluation is performed normally on the data the monitor is based on.
If a monitor is alerting because its current data corresponds to the
resolve has the monitor follow the state switch
ALERT -> OK -> ALERT. Therefore, using
resolve is not appropriate for acknowledging the alert or telling Datadog to ignore the alert.
Manually resolving a monitor is appropriate for cases where data is reported intermittently. For example, after triggering an alert the monitor doesn’t receive further data so it can no longer evaluate alerting conditions and recover to the
OK state. In that case, the
resolve function or the
Automatically resolve monitor after X hours changes the monitor back to an
Typical use case: A monitor based on error metrics that are not generated when there are no errors (
aws.elb.httpcode_elb_5xx, or any DogStatsD counter in your code reporting an error only when there is an error).
Click the settings cog to display the options available:
||Edit the current monitor. See details in the Monitors section.
||Make a copy of the current monitor.
||Export the JSON configuration for the current monitor. This option is also available when creating your monitor. If you manage monitors programmatically, define a monitor in the UI and export the JSON.
||Delete the current monitor. You will be prompted to confirm the deletion.
The properties section is the overview of your monitor’s:
||Alert, Warn, No Data, or OK
||Learn more about monitor types.
||Used for the monitor API.
||The date the monitor was created.
||The person who created the monitor.
||The tags attached at the monitor level. Edit the tags by clicking on the pencil icon.
||Learn more about querying.
||The message specified in the notification section of the monitor.
Status and history
The status and history section displays the query and state changes of your monitor over time. To filter the information, use the search box, statuses, and time selector above the section.
The status graph shows your monitor’s status over time, broken out by group. Note: If you see
no groups found, one of the following situations may apply:
- The monitor is newly created and has not evaluated yet.
- The monitor’s query was recently changed.
- The monitor’s timeframe is too short for a metric that provides data infrequently.
- A host’s name previously included in the query has changed. Hostname changes age out of the UI within 2 hours.
The history graph shows the collected data aligned with the status graph.
The evaluation graph represents the exact query behavior within the timeframe bracket on the history graph. It has a fixed, zoomed window that corresponds to your monitor evaluation time steps to ensure the displayed points are aggregated correctly. Slide this bracket over the timeline to view previous monitor evaluation results:
For further investigation into your metrics evolution, click Open in a notebook by the status graph. This generates an investigation notebook with a formatted graph of the monitor query.
The notebook matches the monitor evaluation period time range and includes related logs where relevant.
Events generated from your monitor (alerts, warnings, recoveries, etc.) are shown in this section based on the time selector above the Status & History section. The events are also displayed in your event stream.
For all monitor types, monitor changes (monitor edits for instance) create an event in the event stream. This event explains the change and displays the user that made the change.
If you made changes to a monitor, you can see examples with the following event search:
Datadog also provides a notification option for changes to monitors you create. At the bottom of the monitor editor, under Notify your team, choose Notify in the drop-down next to: alert recipients when this alert is modified.
The notify setting sends an email with the monitor audit event to all people who are alerted in the specific monitor. The monitor audit event also appears in the event stream.
Export and import
You can obtain a JSON export of any monitor from the monitor’s status page. Click the settings cog (top right) and choose Export from the menu.
Import a monitor to Datadog with JSON using the main navigation: Monitors –> New Monitor –> Import.
Additional helpful documentation, links, and articles: