Datadog Downtime
Search downtimes
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。
Search all scheduled downtimes matching the provided filters. The search is limited to 1000 downtimes.
Inputs
A list of scope values the downtimes should have. Logical operator like OR or AND are not supported in the values. Instead of service:(a OR b), add two values service:a and service:b.
You can also use - to exclude a scope value. For example, -env:staging will return downtimes without the scope env:staging.
A list of monitor tags that the filtered downtimes should have. You can also use - to exclude monitor tags. For example, -env:staging will return downtimes without the monitor tag env:staging.
Only return downtimes that are active when the request is made.
Filter downtimes that are recurring.
Filter downtimes that are automuted.
Maximum number of downtimes in the response.
default: 100
Outputs
Expand All
The list of downtimes that match the search criteria.
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.
