datadog.DowntimeSchedule
Explore with Pulumi AI
Provides a Datadog DowntimeSchedule resource. This can be used to create and manage Datadog downtimes.
Example Usage
Coming soon!
Coming soon!
Coming soon!
Coming soon!
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.datadog.DowntimeSchedule;
import com.pulumi.datadog.DowntimeScheduleArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
// Create new downtime_schedule resource
var downtimeScheduleExample = new DowntimeSchedule("downtimeScheduleExample", DowntimeScheduleArgs.builder()
.scope("env:us9-prod7 AND team:test123")
.monitorIdentifier(DowntimeScheduleMonitorIdentifierArgs.builder()
.monitorTags(
"test:123",
"data:test")
.build())
.recurringSchedule(DowntimeScheduleRecurringScheduleArgs.builder()
.recurrences(DowntimeScheduleRecurringScheduleRecurrenceArgs.builder()
.duration("1h")
.rrule("FREQ=DAILY;INTERVAL=1")
.start("2050-01-02T03:04:05")
.build())
.timezone("America/New_York")
.build())
.displayTimezone("America/New_York")
.message("Message about the downtime")
.muteFirstRecoveryNotification(true)
.notifyEndStates(
"alert",
"warn")
.notifyEndTypes(
"canceled",
"expired")
.build());
}
}
resources:
# Create new downtime_schedule resource
downtimeScheduleExample:
type: datadog:DowntimeSchedule
name: downtime_schedule_example
properties:
scope: env:us9-prod7 AND team:test123
monitorIdentifier:
- monitorTags:
- test:123
- data:test
recurringSchedule:
- recurrences:
- duration: 1h
rrule: FREQ=DAILY;INTERVAL=1
start: 2050-01-02T03:04:05
timezone: America/New_York
displayTimezone: America/New_York
message: Message about the downtime
muteFirstRecoveryNotification: true
notifyEndStates:
- alert
- warn
notifyEndTypes:
- canceled
- expired
Create DowntimeSchedule Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new DowntimeSchedule(name: string, args: DowntimeScheduleArgs, opts?: CustomResourceOptions);
@overload
def DowntimeSchedule(resource_name: str,
args: DowntimeScheduleArgs,
opts: Optional[ResourceOptions] = None)
@overload
def DowntimeSchedule(resource_name: str,
opts: Optional[ResourceOptions] = None,
scope: Optional[str] = None,
display_timezone: Optional[str] = None,
message: Optional[str] = None,
monitor_identifier: Optional[DowntimeScheduleMonitorIdentifierArgs] = None,
mute_first_recovery_notification: Optional[bool] = None,
notify_end_states: Optional[Sequence[str]] = None,
notify_end_types: Optional[Sequence[str]] = None,
one_time_schedule: Optional[DowntimeScheduleOneTimeScheduleArgs] = None,
recurring_schedule: Optional[DowntimeScheduleRecurringScheduleArgs] = None)
func NewDowntimeSchedule(ctx *Context, name string, args DowntimeScheduleArgs, opts ...ResourceOption) (*DowntimeSchedule, error)
public DowntimeSchedule(string name, DowntimeScheduleArgs args, CustomResourceOptions? opts = null)
public DowntimeSchedule(String name, DowntimeScheduleArgs args)
public DowntimeSchedule(String name, DowntimeScheduleArgs args, CustomResourceOptions options)
type: datadog:DowntimeSchedule
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args DowntimeScheduleArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args DowntimeScheduleArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args DowntimeScheduleArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args DowntimeScheduleArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args DowntimeScheduleArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var downtimeScheduleResource = new Datadog.DowntimeSchedule("downtimeScheduleResource", new()
{
Scope = "string",
DisplayTimezone = "string",
Message = "string",
MonitorIdentifier = new Datadog.Inputs.DowntimeScheduleMonitorIdentifierArgs
{
MonitorId = 0,
MonitorTags = new[]
{
"string",
},
},
MuteFirstRecoveryNotification = false,
NotifyEndStates = new[]
{
"string",
},
NotifyEndTypes = new[]
{
"string",
},
OneTimeSchedule = new Datadog.Inputs.DowntimeScheduleOneTimeScheduleArgs
{
End = "string",
Start = "string",
},
RecurringSchedule = new Datadog.Inputs.DowntimeScheduleRecurringScheduleArgs
{
Recurrences = new[]
{
new Datadog.Inputs.DowntimeScheduleRecurringScheduleRecurrenceArgs
{
Duration = "string",
Rrule = "string",
Start = "string",
},
},
Timezone = "string",
},
});
example, err := datadog.NewDowntimeSchedule(ctx, "downtimeScheduleResource", &datadog.DowntimeScheduleArgs{
Scope: pulumi.String("string"),
DisplayTimezone: pulumi.String("string"),
Message: pulumi.String("string"),
MonitorIdentifier: &datadog.DowntimeScheduleMonitorIdentifierArgs{
MonitorId: pulumi.Int(0),
MonitorTags: pulumi.StringArray{
pulumi.String("string"),
},
},
MuteFirstRecoveryNotification: pulumi.Bool(false),
NotifyEndStates: pulumi.StringArray{
pulumi.String("string"),
},
NotifyEndTypes: pulumi.StringArray{
pulumi.String("string"),
},
OneTimeSchedule: &datadog.DowntimeScheduleOneTimeScheduleArgs{
End: pulumi.String("string"),
Start: pulumi.String("string"),
},
RecurringSchedule: &datadog.DowntimeScheduleRecurringScheduleArgs{
Recurrences: datadog.DowntimeScheduleRecurringScheduleRecurrenceArray{
&datadog.DowntimeScheduleRecurringScheduleRecurrenceArgs{
Duration: pulumi.String("string"),
Rrule: pulumi.String("string"),
Start: pulumi.String("string"),
},
},
Timezone: pulumi.String("string"),
},
})
var downtimeScheduleResource = new DowntimeSchedule("downtimeScheduleResource", DowntimeScheduleArgs.builder()
.scope("string")
.displayTimezone("string")
.message("string")
.monitorIdentifier(DowntimeScheduleMonitorIdentifierArgs.builder()
.monitorId(0)
.monitorTags("string")
.build())
.muteFirstRecoveryNotification(false)
.notifyEndStates("string")
.notifyEndTypes("string")
.oneTimeSchedule(DowntimeScheduleOneTimeScheduleArgs.builder()
.end("string")
.start("string")
.build())
.recurringSchedule(DowntimeScheduleRecurringScheduleArgs.builder()
.recurrences(DowntimeScheduleRecurringScheduleRecurrenceArgs.builder()
.duration("string")
.rrule("string")
.start("string")
.build())
.timezone("string")
.build())
.build());
downtime_schedule_resource = datadog.DowntimeSchedule("downtimeScheduleResource",
scope="string",
display_timezone="string",
message="string",
monitor_identifier=datadog.DowntimeScheduleMonitorIdentifierArgs(
monitor_id=0,
monitor_tags=["string"],
),
mute_first_recovery_notification=False,
notify_end_states=["string"],
notify_end_types=["string"],
one_time_schedule=datadog.DowntimeScheduleOneTimeScheduleArgs(
end="string",
start="string",
),
recurring_schedule=datadog.DowntimeScheduleRecurringScheduleArgs(
recurrences=[datadog.DowntimeScheduleRecurringScheduleRecurrenceArgs(
duration="string",
rrule="string",
start="string",
)],
timezone="string",
))
const downtimeScheduleResource = new datadog.DowntimeSchedule("downtimeScheduleResource", {
scope: "string",
displayTimezone: "string",
message: "string",
monitorIdentifier: {
monitorId: 0,
monitorTags: ["string"],
},
muteFirstRecoveryNotification: false,
notifyEndStates: ["string"],
notifyEndTypes: ["string"],
oneTimeSchedule: {
end: "string",
start: "string",
},
recurringSchedule: {
recurrences: [{
duration: "string",
rrule: "string",
start: "string",
}],
timezone: "string",
},
});
type: datadog:DowntimeSchedule
properties:
displayTimezone: string
message: string
monitorIdentifier:
monitorId: 0
monitorTags:
- string
muteFirstRecoveryNotification: false
notifyEndStates:
- string
notifyEndTypes:
- string
oneTimeSchedule:
end: string
start: string
recurringSchedule:
recurrences:
- duration: string
rrule: string
start: string
timezone: string
scope: string
DowntimeSchedule Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The DowntimeSchedule resource accepts the following input properties:
- Scope string
- The scope to which the downtime applies. Must follow the common search syntax.
- Display
Timezone 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. - Monitor
Identifier DowntimeSchedule Monitor Identifier - Mute
First boolRecovery Notification - If the first recovery notification during a downtime should be muted.
- Notify
End List<string>States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - Notify
End List<string>Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - One
Time DowntimeSchedule Schedule One Time Schedule - Recurring
Schedule DowntimeSchedule Recurring Schedule
- Scope string
- The scope to which the downtime applies. Must follow the common search syntax.
- Display
Timezone 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. - Monitor
Identifier DowntimeSchedule Monitor Identifier Args - Mute
First boolRecovery Notification - If the first recovery notification during a downtime should be muted.
- Notify
End []stringStates - States that will trigger a monitor notification when the
notify_end_types
action occurs. - Notify
End []stringTypes - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - One
Time DowntimeSchedule Schedule One Time Schedule Args - Recurring
Schedule DowntimeSchedule Recurring Schedule Args
- scope String
- The scope to which the downtime applies. Must follow the common search syntax.
- display
Timezone 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. - monitor
Identifier DowntimeSchedule Monitor Identifier - mute
First BooleanRecovery Notification - If the first recovery notification during a downtime should be muted.
- notify
End List<String>States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify
End List<String>Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one
Time DowntimeSchedule Schedule One Time Schedule - recurring
Schedule DowntimeSchedule Recurring Schedule
- scope string
- The scope to which the downtime applies. Must follow the common search syntax.
- display
Timezone 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. - monitor
Identifier DowntimeSchedule Monitor Identifier - mute
First booleanRecovery Notification - If the first recovery notification during a downtime should be muted.
- notify
End string[]States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify
End string[]Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one
Time DowntimeSchedule Schedule One Time Schedule - recurring
Schedule DowntimeSchedule Recurring Schedule
- scope str
- The scope to which the downtime applies. Must follow the common search syntax.
- display_
timezone str - 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 str
- 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. - monitor_
identifier DowntimeSchedule Monitor Identifier Args - mute_
first_ boolrecovery_ notification - If the first recovery notification during a downtime should be muted.
- notify_
end_ Sequence[str]states - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify_
end_ Sequence[str]types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one_
time_ Downtimeschedule Schedule One Time Schedule Args - recurring_
schedule DowntimeSchedule Recurring Schedule Args
- scope String
- The scope to which the downtime applies. Must follow the common search syntax.
- display
Timezone 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. - monitor
Identifier Property Map - mute
First BooleanRecovery Notification - If the first recovery notification during a downtime should be muted.
- notify
End List<String>States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify
End List<String>Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one
Time Property MapSchedule - recurring
Schedule Property Map
Outputs
All input properties are implicitly available as output properties. Additionally, the DowntimeSchedule resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing DowntimeSchedule Resource
Get an existing DowntimeSchedule resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: DowntimeScheduleState, opts?: CustomResourceOptions): DowntimeSchedule
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
display_timezone: Optional[str] = None,
message: Optional[str] = None,
monitor_identifier: Optional[DowntimeScheduleMonitorIdentifierArgs] = None,
mute_first_recovery_notification: Optional[bool] = None,
notify_end_states: Optional[Sequence[str]] = None,
notify_end_types: Optional[Sequence[str]] = None,
one_time_schedule: Optional[DowntimeScheduleOneTimeScheduleArgs] = None,
recurring_schedule: Optional[DowntimeScheduleRecurringScheduleArgs] = None,
scope: Optional[str] = None) -> DowntimeSchedule
func GetDowntimeSchedule(ctx *Context, name string, id IDInput, state *DowntimeScheduleState, opts ...ResourceOption) (*DowntimeSchedule, error)
public static DowntimeSchedule Get(string name, Input<string> id, DowntimeScheduleState? state, CustomResourceOptions? opts = null)
public static DowntimeSchedule get(String name, Output<String> id, DowntimeScheduleState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Display
Timezone 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. - Monitor
Identifier DowntimeSchedule Monitor Identifier - Mute
First boolRecovery Notification - If the first recovery notification during a downtime should be muted.
- Notify
End List<string>States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - Notify
End List<string>Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - One
Time DowntimeSchedule Schedule One Time Schedule - Recurring
Schedule DowntimeSchedule Recurring Schedule - Scope string
- The scope to which the downtime applies. Must follow the common search syntax.
- Display
Timezone 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. - Monitor
Identifier DowntimeSchedule Monitor Identifier Args - Mute
First boolRecovery Notification - If the first recovery notification during a downtime should be muted.
- Notify
End []stringStates - States that will trigger a monitor notification when the
notify_end_types
action occurs. - Notify
End []stringTypes - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - One
Time DowntimeSchedule Schedule One Time Schedule Args - Recurring
Schedule DowntimeSchedule Recurring Schedule Args - Scope string
- The scope to which the downtime applies. Must follow the common search syntax.
- display
Timezone 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. - monitor
Identifier DowntimeSchedule Monitor Identifier - mute
First BooleanRecovery Notification - If the first recovery notification during a downtime should be muted.
- notify
End List<String>States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify
End List<String>Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one
Time DowntimeSchedule Schedule One Time Schedule - recurring
Schedule DowntimeSchedule Recurring Schedule - scope String
- The scope to which the downtime applies. Must follow the common search syntax.
- display
Timezone 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. - monitor
Identifier DowntimeSchedule Monitor Identifier - mute
First booleanRecovery Notification - If the first recovery notification during a downtime should be muted.
- notify
End string[]States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify
End string[]Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one
Time DowntimeSchedule Schedule One Time Schedule - recurring
Schedule DowntimeSchedule Recurring Schedule - scope string
- The scope to which the downtime applies. Must follow the common search syntax.
- display_
timezone str - 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 str
- 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. - monitor_
identifier DowntimeSchedule Monitor Identifier Args - mute_
first_ boolrecovery_ notification - If the first recovery notification during a downtime should be muted.
- notify_
end_ Sequence[str]states - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify_
end_ Sequence[str]types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one_
time_ Downtimeschedule Schedule One Time Schedule Args - recurring_
schedule DowntimeSchedule Recurring Schedule Args - scope str
- The scope to which the downtime applies. Must follow the common search syntax.
- display
Timezone 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. - monitor
Identifier Property Map - mute
First BooleanRecovery Notification - If the first recovery notification during a downtime should be muted.
- notify
End List<String>States - States that will trigger a monitor notification when the
notify_end_types
action occurs. - notify
End List<String>Types - Actions that will trigger a monitor notification if the downtime is in the
notify_end_types
state. - one
Time Property MapSchedule - recurring
Schedule Property Map - scope String
- The scope to which the downtime applies. Must follow the common search syntax.
Supporting Types
DowntimeScheduleMonitorIdentifier, DowntimeScheduleMonitorIdentifierArgs
- Monitor
Id int - ID of the monitor to prevent notifications.
- List<string>
- A 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. Setting
monitor_tags
to[*]
configures the downtime to mute all monitors for the given scope.
- Monitor
Id int - ID of the monitor to prevent notifications.
- []string
- A 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. Setting
monitor_tags
to[*]
configures the downtime to mute all monitors for the given scope.
- monitor
Id Integer - ID of the monitor to prevent notifications.
- List<String>
- A 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. Setting
monitor_tags
to[*]
configures the downtime to mute all monitors for the given scope.
- monitor
Id number - ID of the monitor to prevent notifications.
- string[]
- A 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. Setting
monitor_tags
to[*]
configures the downtime to mute all monitors for the given scope.
- monitor_
id int - ID of the monitor to prevent notifications.
- Sequence[str]
- A 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. Setting
monitor_tags
to[*]
configures the downtime to mute all monitors for the given scope.
- monitor
Id Number - ID of the monitor to prevent notifications.
- List<String>
- A 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. Setting
monitor_tags
to[*]
configures the downtime to mute all monitors for the given scope.
DowntimeScheduleOneTimeSchedule, DowntimeScheduleOneTimeScheduleArgs
DowntimeScheduleRecurringSchedule, DowntimeScheduleRecurringScheduleArgs
- Recurrences
List<Downtime
Schedule Recurring Schedule Recurrence> - Timezone string
- The timezone in which to schedule the downtime.
- Recurrences
[]Downtime
Schedule Recurring Schedule Recurrence - Timezone string
- The timezone in which to schedule the downtime.
- recurrences
List<Downtime
Schedule Recurring Schedule Recurrence> - timezone String
- The timezone in which to schedule the downtime.
- recurrences
Downtime
Schedule Recurring Schedule Recurrence[] - timezone string
- The timezone in which to schedule the downtime.
- recurrences
Sequence[Downtime
Schedule Recurring Schedule Recurrence] - timezone str
- The timezone in which to schedule the downtime.
- recurrences List<Property Map>
- timezone String
- The timezone in which to schedule the downtime.
DowntimeScheduleRecurringScheduleRecurrence, DowntimeScheduleRecurringScheduleRecurrenceArgs
- Duration string
- The length of the downtime. Must begin with an integer and end with one of 'm', 'h', d', or 'w'.
- Rrule string
- The
RRULE
standard for defining recurring events. For example, to have a recurring event on the first day of each month, set the type torrule
and set theFREQ
toMONTHLY
andBYMONTHDAY
to1
. Most commonrrule
options from the iCalendar Spec are supported. Note: Attributes specifying the duration inRRULE
are not supported (for example,DTSTART
,DTEND
,DURATION
). More examples available in this downtime guide. - Start string
- ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.
- Duration string
- The length of the downtime. Must begin with an integer and end with one of 'm', 'h', d', or 'w'.
- Rrule string
- The
RRULE
standard for defining recurring events. For example, to have a recurring event on the first day of each month, set the type torrule
and set theFREQ
toMONTHLY
andBYMONTHDAY
to1
. Most commonrrule
options from the iCalendar Spec are supported. Note: Attributes specifying the duration inRRULE
are not supported (for example,DTSTART
,DTEND
,DURATION
). More examples available in this downtime guide. - Start string
- ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.
- duration String
- The length of the downtime. Must begin with an integer and end with one of 'm', 'h', d', or 'w'.
- rrule String
- The
RRULE
standard for defining recurring events. For example, to have a recurring event on the first day of each month, set the type torrule
and set theFREQ
toMONTHLY
andBYMONTHDAY
to1
. Most commonrrule
options from the iCalendar Spec are supported. Note: Attributes specifying the duration inRRULE
are not supported (for example,DTSTART
,DTEND
,DURATION
). More examples available in this downtime guide. - start String
- ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.
- duration string
- The length of the downtime. Must begin with an integer and end with one of 'm', 'h', d', or 'w'.
- rrule string
- The
RRULE
standard for defining recurring events. For example, to have a recurring event on the first day of each month, set the type torrule
and set theFREQ
toMONTHLY
andBYMONTHDAY
to1
. Most commonrrule
options from the iCalendar Spec are supported. Note: Attributes specifying the duration inRRULE
are not supported (for example,DTSTART
,DTEND
,DURATION
). More examples available in this downtime guide. - start string
- ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.
- duration str
- The length of the downtime. Must begin with an integer and end with one of 'm', 'h', d', or 'w'.
- rrule str
- The
RRULE
standard for defining recurring events. For example, to have a recurring event on the first day of each month, set the type torrule
and set theFREQ
toMONTHLY
andBYMONTHDAY
to1
. Most commonrrule
options from the iCalendar Spec are supported. Note: Attributes specifying the duration inRRULE
are not supported (for example,DTSTART
,DTEND
,DURATION
). More examples available in this downtime guide. - start str
- ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.
- duration String
- The length of the downtime. Must begin with an integer and end with one of 'm', 'h', d', or 'w'.
- rrule String
- The
RRULE
standard for defining recurring events. For example, to have a recurring event on the first day of each month, set the type torrule
and set theFREQ
toMONTHLY
andBYMONTHDAY
to1
. Most commonrrule
options from the iCalendar Spec are supported. Note: Attributes specifying the duration inRRULE
are not supported (for example,DTSTART
,DTEND
,DURATION
). More examples available in this downtime guide. - start String
- ISO-8601 Datetime to start the downtime. Must not include a UTC offset. If not provided, the downtime starts the moment it is created.
Import
$ pulumi import datadog:index/downtimeSchedule:DowntimeSchedule new_list "00e000000-0000-1234-0000-000000000000"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- Datadog pulumi/pulumi-datadog
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
datadog
Terraform Provider.