You may occasionally need to shut systems down or take them off-line to perform maintenance or upgrades. Scheduling downtime allows you to do this without triggering monitors.
You can schedule downtimes and/or mute your Datadog monitors so that they do not alert at specific times when you do not want them to.
Monitors trigger events when they change state between ALERT, WARNING (if enabled), RESOLVED, and NO DATA (if enabled). But if a monitor has been silenced either by a downtime or muting, then any transition from RESOLVED to another state won’t trigger an event (nor the notification channels that the event would have set off).
If a monitor transitions states during downtime (such as from OK to ALERT, WARNING, or NO DATA) and remains in that state once a scheduled downtime expires, it will NOT trigger a notification. However it WILL trigger a recovery event once data returns for that scope or the monitor returns to an OK state.
This may seem unintuitive, but it is the expected behavior today, and it has been made this way to protect from potentially spammy no-data alerts when using the “Autoresolve” feature. If in these circumstances you would prefer that the monitor triggers a NO DATA event at the time that the silencing expires, there is a feature you can have enabled for your account to enable that behavior. To have that enabled, you can reach out to the support team to request it. This will only affect instances when a monitor exits a downtime period in a NO DATA state.
Navigate to the Manage Downtime page by highlighting the “Monitors” tab in the main menu and selecting the “Manage Downtime” link. You may also navigate to the “Manage Downtime” page from other Monitor related pages by clicking the link at the top of the page.
The Manage Downtime page displays a list of active and scheduled downtimes. Select a downtime to view more details about the host and monitors affected.
To schedule downtime, click the “Schedule Downtime” button in the upper right.
Choose what to silence.
You can select a specific monitor to silence, or leave this field empty to silence all monitors. You can also select a scope to constrain your downtime to a specific host, device or arbitrary tag.
Refer to the scope section of the Graphing Primer using JSON for further information about scope.
If you choose to silence all monitors constrained by a scope, clicking the “Preview affected monitors” shows which monitors are currently affected. Any monitors within your scope that are created or edited after the downtime is schedule is also silenced.
Note that if a multi alert is included, it is only silenced for systems covered by the scope. For example, if a downtime scope is set for
host:X and a multi alert is triggered on both
host:Y, Datadog generates a monitor notification for
host:Y, but not
Set a schedule. You can set a start date and time or leave the field empty to immediately start the downtime. You may also set a repeating schedule to accommodate regularly scheduled downtimes.
Add an optional message to notify your team Enter a message to notify your team about this downtime. The message field allows standard markdown formatting as well as Datadog’s @-notification syntax. The “Notify your team” field allows you to specify team members or send the message to a service integration.