Optional
activeIf a scheduled downtime currently exists.
Optional
additionalA container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.
Optional
canceledIf a scheduled downtime is canceled.
Optional
creatorUser ID of the downtime creator.
Optional
disabledIf a downtime has been disabled.
Optional
downtime0
for a downtime applied on *
or all,
1
when the downtime is only scoped to hosts,
or 2
when the downtime is scoped to anything but hosts.
Optional
endPOSIX timestamp to end the downtime. If not provided, the downtime is in effect indefinitely until you cancel it.
Optional
idThe downtime ID.
Optional
messageA message to include with notifications for this downtime.
Email notifications can be sent to specific users by using the same @username
notation as events.
Optional
monitorA single monitor to which the downtime applies. If not provided, the downtime applies to all monitors.
Optional
monitorA comma-separated list of monitor tags. For example, tags that are applied directly to monitors,
not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies.
The resulting downtime applies to monitors that match ALL provided monitor tags.
For example, service:postgres
AND team:frontend
.
Optional
muteIf the first recovery notification during a downtime should be muted.
Optional
notifyStates for which notify_end_types
sends out notifications for.
Optional
notifyIf set, notifies if a monitor is in an alert-worthy state (ALERT
, WARNING
, or NO DATA
)
when this downtime expires or is canceled. Applied to monitors that change states during
the downtime (such as from OK
to ALERT
, WARNING
, or NO DATA
), and to monitors that
already have an alert-worthy state when downtime begins.
Optional
parentID of the parent Downtime.
Optional
recurrenceAn object defining the recurrence of the downtime.
Optional
scopeThe scope(s) to which the downtime applies and must be in key:value
format. For example, host:app2
.
Provide multiple scopes as a comma-separated list like env:dev,env:prod
.
The resulting downtime applies to sources that matches ALL provided scopes (env:dev
AND env:prod
).
Optional
startPOSIX timestamp to start the downtime. If not provided, the downtime starts the moment it is created.
Optional
timezoneThe timezone in which to display the downtime's start and end times in Datadog applications.
Optional
updaterID of the last user that updated the downtime.
Generated using TypeDoc
The downtime object definition of the active child for the original parent recurring downtime. This field will only exist on recurring downtimes.