Schedule maintenance windows so planned downtime on selected monitors does not raise alarms or count against availability. Windows can run once or on a recurring schedule and apply to individual monitors or a monitor group.
Scheduled Maintenance lets administrators define maintenance windows during which the associated monitors are placed in maintenance. While a window is active, downtime on those monitors is treated as planned, so it does not generate alarms or reduce the availability figures for the affected entities. This is used for planned activities such as patching, reboots, or network changes, where a device is expected to go offline and should not trigger notifications.
Each maintenance window is defined by what it applies to, how often and for how long it runs, and the overall date range the schedule is active within. Navigate to Settings → Configurations → Scheduled Maintenance to view, add, and manage maintenance windows. The page has two tabs: Scheduled Maintenance, which lists the configured windows, and Maintenance History, which records past maintenance activity.
Navigate to Settings → Configurations → Scheduled Maintenance and click Add. The Add Scheduled Maintenance form is divided into three sections.
Maintenance Details
| Field | Description |
| Display Name | A name to identify this maintenance window in the Scheduled Maintenance list. |
| Description | An optional description of the window's purpose. |
| Time Zone | The time zone the maintenance schedule runs in. Start times and recurrence are evaluated against this time zone. |
| Association Type | Whether the window applies to individual Monitor entities or to a Monitor Group. |
| Monitors / Monitor Group | The specific monitors, or the monitor group, to place in maintenance while the window is active. The field matches the selected Association Type. |
Recurrence Details
Defines how often, and for how long, the maintenance window runs. The available recurrence options adapt to the selected Frequency.
| Field | Description |
| Frequency | How often the window recurs: Once, Daily, Weekly, Monthly, or Yearly. |
| Set Recurrence | Whether the recurring schedule is defined By Day or By Time. |
| Day(s) | The days of the week the window runs on (Sunday to Saturday), or All Day to cover the whole day. |
| Start Time | The time the maintenance window begins, in hours and minutes with AM or PM. |
| Maintenance Duration (Mins) | How long the window stays active, in minutes. |
| Repeats every | The recurrence interval, such as every set number of weeks, for a repeating schedule. |
Maintenance Window
Sets the overall date range the recurring schedule is active within.
| Field | Description |
| Start the Maintenance On | The date the recurring schedule becomes active. |
| End the Maintenance | When the recurring schedule stops: Never, After a set number of occurrences, or On a specific date. |
Click Save to create the maintenance window, or Reset to clear the form. The window appears in the Scheduled Maintenance list with its name, time zone, frequency, status, association type, and associations, and can be edited or deleted from the Actions column.
The Maintenance History tab records maintenance activity that has already run, providing an audit trail of when monitors were placed in maintenance and for how long. Use it to confirm that a planned window took effect as configured, and to review past maintenance when investigating a gap in availability data.
| Issue | What to check |
| Alarms still fired during a planned window | Confirm the affected monitors are included in the window's associations, and that the window was active at the time. Check the Time Zone, Start Time, and Maintenance Duration, since the window is evaluated against the configured time zone rather than the viewer's local time. |
| The window did not run when expected | Check the Maintenance Window date range: a recurring schedule only runs between Start the Maintenance On and its end condition. Confirm the window has not already reached its End the Maintenance limit. |
| A newly added device is not covered | Where the Association Type is Monitor, only the individually selected monitors are covered. Use a Monitor Group association so that devices added to the group are covered without editing each window. |