Class: DatadogAPIClient::V2::DowntimeScheduleRecurrenceCreateUpdateRequest

Inherits:
Object
  • Object
show all
Includes:
BaseGenericModel
Defined in:
lib/datadog_api_client/v2/models/downtime_schedule_recurrence_create_update_request.rb

Overview

An object defining the recurrence of the downtime.

Instance Attribute Summary collapse

Method Summary

Methods included from BaseGenericModel

included

Instance Attribute Details

#additional_properties ⇒ Object

Returns the value of attribute additional_properties.



39
40
41
 
# File 'lib/datadog_api_client/v2/models/downtime_schedule_recurrence_create_update_request.rb', line 39

def additional_properties
  @additional_properties
end

#duration ⇒ Object

The length of the downtime. Must begin with an integer and end with one of ‘m’, ‘h’, d’, or ‘w’.



25
26
27
 
# File 'lib/datadog_api_client/v2/models/downtime_schedule_recurrence_create_update_request.rb', line 25

def duration
  @duration
end

#rrule ⇒ Object

The ‘RRULE` standard for defining recurring events. 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`. Most common `rrule` options from the [iCalendar Spec](tools.ietf.org/html/rfc5545) are supported.

Note: Attributes specifying the duration in ‘RRULE` are not supported (for example, `DTSTART`, `DTEND`, `DURATION`). More examples available in this [downtime guide](docs.datadoghq.com/monitors/guide/suppress-alert-with-downtimes/?tab=api).



33
34
35
 
# File 'lib/datadog_api_client/v2/models/downtime_schedule_recurrence_create_update_request.rb', line 33

def rrule
  @rrule
end

#start ⇒ Object

ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.



37
38
39
 
# File 'lib/datadog_api_client/v2/models/downtime_schedule_recurrence_create_update_request.rb', line 37

def start
  @start
end