Downtime details.

Hierarchy

  • DowntimeResponseAttributes

Constructors

Properties

additionalProperties?: {
    [key: string]: any;
}

A container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.

Type declaration

  • [key: string]: any
canceled?: Date

Time that the downtime was canceled.

created?: Date

Creation time of the downtime.

displayTimezone?: string

The timezone in which to display the downtime's start and end times in Datadog applications. This is not used as an offset for scheduling.

message?: string

A message to include with notifications for this downtime. Email notifications can be sent to specific users by using the same @username notation as events.

modified?: Date

Time that the downtime was last modified.

monitorIdentifier?: DowntimeMonitorIdentifier

Monitor identifier for the downtime.

muteFirstRecoveryNotification?: boolean

If the first recovery notification during a downtime should be muted.

notifyEndStates?: DowntimeNotifyEndStateTypes[]

States that will trigger a monitor notification when the notify_end_types action occurs.

Actions that will trigger a monitor notification if the downtime is in the notify_end_types state.

The principals (users, roles, or teams) allowed to act on behalf of the downtime.

Note: This feature is currently in Preview and may not be available for all organizations.

The schedule that defines when the monitor starts, stops, and recurs. There are two types of schedules: one-time and recurring. Recurring schedules may have up to five RRULE-based recurrences. If no schedules are provided, the downtime will begin immediately and never end.

scope?: string

The scope to which the downtime applies. Must follow the common search syntax.

The current status of the downtime.

Generated using TypeDoc