-
Notifications
You must be signed in to change notification settings - Fork 1
2.2 One Time Maintenances
This maintenance window type can either span across two days or two dates, depending on the setup. Spanning across multiple dates is simply achieved by adding the end date to the definition. If the end time of the definition is smaller than the start time, it will leak into the next day until it ends, see examples for a better explanation of it. While you can set them up within PRTG, only this way they'll show up in the maintenance report.
maintenance[<[timezone]>|<start date>|[<end date>]|start|end|<[description]>]
Values in brackets are optional, the rest needs to be there.
Column | Description |
---|---|
timezone | This is the timezone that will be applied to the maintenance window. When omitted, the default timezone will be used. |
start date | The start date in the format dd/mm/YYYY |
end date | The end date of the maintenance Window in the format dd/mm/YYYY |
start time | The start time of the maintenance window in 24h format, e.g. 23:00 |
end time | The end time of the maintenance window in 24h format, e.g. 23:30 |
description | A description of the maintenance window. It will show up in the report and help to keep track of them |
maintenance[20/06/2017|20:00|22:00|Maintenance Window]
Start Date | Start | End | Description |
---|---|---|---|
20/06/2017 | 20:00 | 22:00 | Maintenance Window |
On the 20th of June 2017, from 8pm to 10pm
maintenance[20/06/2017|20:00|1:30|Maintenance Window]
Start Date | End Date | Start | End | Description |
---|---|---|---|---|
20/06/2017 | 23/06/2017 | 20:00 | 1:30 | Maintenance Window |
From June 20th, 8pm to June 21st, 1:30am
maintenance[20/06/2017|23/06/2017|20:00|1:30|Maintenance Window]
Start Date | End Date | Start | End | Description |
---|---|---|---|---|
20/06/2017 | 23/06/2017 | 20:00 | 1:30 | Maintenance Window |
From June 20th, 8pm to June 23rd, 1:30am