Datadog Downtime
List downtimes
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.
Get all scheduled downtimes.
Inputs
Only return downtimes that are active when the request is made.
Outputs
Expand All
If a scheduled downtime currently exists.
If a scheduled downtime is canceled.
User ID of the downtime creator.
If a downtime has been disabled.
0 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.
POSIX timestamp to end the downtime.
A message to include with notifications for this downtime.
A single monitor to which the downtime applies.
A comma-separated list of monitor tags.
ID of the parent Downtime.
An object defining the recurrence of the downtime.
How often to repeat as an integer.
The RRULE standard for defining recurring events (requires to set "type" to rrule) For example, to have a recurring event on the first day of each month, set the type to rrule and set the FREQ to MONTHLY and BYMONTHDAY to 1.
The date at which the recurrence should end as a POSIX timestamp.
How many times the downtime is rescheduled.
A list of week days to repeat on.
The scope(s) to which the downtime applies.
POSIX timestamp to start the downtime.
The timezone in which to display the downtime's start and end times in Datadog applications.
ID of the last user that updated the downtime.
The downtime object definition of the active child for the original parent recurring downtime.
If a scheduled downtime currently exists.
If a scheduled downtime is canceled.
User ID of the downtime creator.
If a downtime has been disabled.
0 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.
POSIX timestamp to end the downtime.
A message to include with notifications for this downtime.
A single monitor to which the downtime applies.
A comma-separated list of monitor tags.
ID of the parent Downtime.
An object defining the recurrence of the downtime.
How often to repeat as an integer.
The RRULE standard for defining recurring events (requires to set "type" to rrule) For example, to have a recurring event on the first day of each month, set the type to rrule and set the FREQ to MONTHLY and BYMONTHDAY to 1.
The date at which the recurrence should end as a POSIX timestamp.
How many times the downtime is rescheduled.
A list of week days to repeat on.
The scope(s) to which the downtime applies.
POSIX timestamp to start the downtime.
The timezone in which to display the downtime's start and end times in Datadog applications.
ID of the last user that updated the downtime.
