Create recurring schedule – weekly pattern
This endpoint is used to create a weekly recurring schedule.
URL
POST https://{api-url}/api/v2/tenants/{tenantId}/scheduleMaintenances
Sample URLs
https://{api-url}/api/v2/tenants/client_93/scheduleMaintenances
Parameters
Field | Data Type | Description |
---|
name | String | Schedule name. |
description | String | Schedule description. |
devices/deviceGroups/locations | String | Details of resources which should be added to schedule maintenance window. No more than 100 resources can be added to a schedule maintenance window. |
schedule- type
- startTime
- endTime
- timezone
- pattern
- type
- weekDays
| String | Schedule details:- Schedule type.
- Time at which the schedule activity should begin.
- Time at which the schedule activity should end.
- Timezone in which the schedule should operate. (The list of timezones are shown below.)
Example: "timezone": "America/Puerto_Rico" - Schedule pattern:
- Pattern type.
- Weekday pattern with these values: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday.
|
runRBA | Boolean | (Optional) Set runRBA=true to run RBA scripts; otherwise, set to false. |
installPatch | Boolean | (Optional) Set installPatch=true to install patch; otherwise, set to false. |
endBy | String | (Optional) Maintenance ending schedule.- For a recurring schedule maintenance to be perpetual, provide endBy: NEVER. In this case, time specified in the field endTime is the scheduled end time. (The date is *not* considered by the API.) To assign a schedule maintenance to run on alternate days, it starts at 8 AM and ends at 5:30 PM. Maintenance is to be set as a repetitive process that never ends. The values provided are:
"schedule": { "type": "Recurring", "startTime": "2018-05-28T08:00:00+0000", "endTime": "2018-10-29T17:30:00+0000", "timezone": "America/Puerto_Rico", "pattern": "type": "daily", "dayFrequency": "everyday" "repeatFrequency": 1 "endBy": "Never" } } - For a recurring schedule maintenance to end at a specific time period, provide the end date and time in the field endTime. Example: "2016-05-29T18:55:27+0000"
|
installPatch | Boolean | (Optional) Set installPatch=true to install patch. |
runEscalationAction | Boolean | (Optional) Provide runEscalationAction: true to escalate maintenance alerts after schedule maintenance is completed. If no value is provided, the default value is true. |
alertConditions- matchingType
- rules
- key
- operator
- value
| String | (Optional) For specific alerts to be triggered as maintenance alerts, configure the below alert conditions. Alerts that do match with the below conditions are triggered as monitoring alerts:- Alert conditions should match ALL or ANY of the rules.
- Conditions for filter alerts:
- Unique attribute of alert.
- Logical operators to filter alertsSupported values: Equals, NotEquals, Equals, NotEquals, Startswith, Endswith, Regex. See Regular Expressions to filter alerts with operator Regex.
- Unique data of alert.
Example: Cloud Controller Discovery
|
Timezones |
---|
Pacific/Asia | Pacific/Honolulu | America/Anchorage |
America/Los_Angeles | America/Denver | America/Chicago |
America/New_York | America/Puerto_Rico | America/St_Johns |
America/Buenos_Aires | Atlantic/Azores | Europe/London |
Europe/Paris | Europe/Istanbul | Africa/Addis_Ababa |
Asia/Tehran | Asia/Yerevan | Asia/Karachi |
Asia/Calcutta | Asia/Dacca | Asia/Saigon |
Asia/Shanghai | Asia/Tokyo | Australia/Darwin |
Australia/Sydney | Pacific/Guadalcanal | Pacific/Auckland |
Sample request
{
"name": "Recurring-weeklyschedule",
"description": "Recurring-weeklyschedule",
"runRBA": "false",
"installPatch": "false",
"devices": [{
"hostName": "Device_1"
},
{
"uniqueId": "90491678-096c-4223-9867-f31c37ff09da"
}
],
"deviceGroups": [{
"name": "DG-1"
},
{
"id": "11"
}
],
"locations": [{
"name": "LOC-1"
},
{
"id": "12"
}
],
"schedule": {
"type": "Recurring",
"startTime": "2015-05-28T10:55:27+0000",
"endTime": "2015-05-29T18:55:27+0000",
"timezone": "America/Puerto_Rico",
"pattern": {
"type": "weekly",
"weekDays": "Wednesday,Thursday"
}
}
}
Sample response
{
"uniqueId": "SM-d21b6b44-c85a-426c-9963-0e977070ce98"
}