Uptime Monitoring: Maintenance

Updated

Uptime Monitoring: Maintenance

Overview

Use this page to schedule and manage maintenance windows that pause uptime checks during planned downtime. A maintenance window is a scheduled interval, scoped to all checks or a specific subset, during which the checks it covers stop running. This keeps planned changes, patching, or other known outages from generating false alerts or incidents while the work is in progress.

Maintenance windows apply to the uptime checks created on the Checks page. A window covers All checks by default, which also includes checks you add later, or only the checks you pick. While a window is active, the checks it covers do not run and show the status Maintenance, so no new incidents are generated from them, and that gap is visible afterward on the Dashboards and Incidents pages. An incident that was already open when the window started stays open through it.

This page lists every window in a single table, sorted by start, showing its name, the checks it covers, its start and end time, recurrence, and reason. The list does not mark which windows are active, upcoming, or past, and a one-time window stays listed after it ends until you delete it. From here you can open a window to review or edit its details, delete a window that is no longer needed, or create a new one for an upcoming change.

Key concepts

  • maintenance window - A scheduled interval, scoped to all or specific uptime checks, during which those checks stop running so planned downtime does not trigger alerts. (related: Uptime Monitoring: Checks)
  • uptime check - The periodic probe that monitors a target's availability; a maintenance window covers all checks or the checks you pick. (related: Uptime Monitoring: Checks)
  • recurrence - A window runs once (One Time) or repeats Daily, Weekly on the days you pick, or Monthly on the days of the month you pick, where day 31 means the last day of the month. A repeating window takes a time of day, not a date, and runs past midnight when its end time is earlier than its start time.
  • time zone - Start and End are entered and shown in the appliance time zone, which the Times in chip names. A repeating window keeps the time zone it was saved in, so it stays at the same local time when daylight saving time starts or ends.

When to use it

  • Before a planned infrastructure change, deployment, or patch window where the affected services are expected to go down.
  • To silence a known, scheduled outage instead of manually pausing or acknowledging each uptime check.
  • To review the scheduled maintenance windows and their times before troubleshooting an unexpected alert.
  • To edit a scheduled window whose start time, end time, or scope changed.
  • To delete a window that is no longer needed, for example after a maintenance plan was cancelled.

Before you begin

  • To limit a window to specific checks, create those checks first on the Uptime Monitoring: Checks page; a window set to All checks also covers checks you add later.
  • Know the exact planned start and end time of the downtime, in the timezone shown by the Times in chip in the top bar.
  • Confirm which checks the planned work affects, so you can scope the window to All checks or to the specific ones involved.

Common workflows

Review scheduled maintenance windows

Persona: Load-test operator

  1. Open the Maintenance page under Uptime Monitoring.
    • Expect: The Maintenance Windows table loads, listing each scheduled window with its Checks, Start, End, Recurrence, and Reason.
  2. Read the Times in chip in the top bar. On a narrow screen the chip is hidden; the New Maintenance Window dialog names the zone too.
    • Expect: You confirm the timezone that the Start and End columns use, so the listed downtime matches the planned schedule.

Verify: The table shows the expected window with the correct Checks scope and Start/End times for the planned downtime.

Edit an existing maintenance window

Persona: Admin

  1. Select the Edit icon on the window's row.
    • Expect: The Edit Maintenance Window dialog opens, pre-filled with the window's current Name, Reason, Recurrence, Start, End, and Affected Checks.
  2. Update the fields that changed and select Save Changes.
    • Expect: The dialog closes and the row in the table reflects the updated values.

Verify: The table row shows the new Start, End, or Reason value you just entered.

Delete a maintenance window

Persona: Admin

  1. Select the Delete icon on the window's row.
    • Expect: A Delete Maintenance Window confirmation prompt appears.
  2. Confirm the deletion.
    • Expect: The row is removed from the table and the checks it covered return to their normal, unpaused schedule.

Verify: The window no longer appears in the table; if it was the only one scheduled, the table shows No maintenance windows.

Steps

Step 1

Select Maintenance under Uptime Monitoring.

Expected result: The Maintenance Windows table loads, listing each scheduled window with its Name, Checks, Start, End, Recurrence, and Reason; Start and End are rendered in the timezone shown by the Times in chip.

This table is the starting point for reviewing, editing, or deleting any planned pause in uptime checks.

  • The Times in chip in the top bar shows the timezone used by the Start and End columns. It is hidden on narrow screens; the window dialog names the zone as well.
  • Each row has Edit (pencil) and Delete (trash) icons under Actions.
  • If no windows are scheduled, the table shows No maintenance windows instead of a row, with a Create Window button. Uptime Monitoring: Maintenance - step 1

Column reference

Column What it shows How to read it
Name Identifies the maintenance window in the table so you can recognize it at a glance. This is the label assigned when the window was created; it does not affect which checks are paused.
Checks Shows which uptime checks this window pauses. All means every check is paused for the duration of the window, including checks added later; a window limited to specific checks shows how many, for example 2 checks. Open it with Edit to see which.
Start The date and time the pause begins; for a repeating window, only the time of day. The covered checks stop running at this time, rendered in the timezone shown by the Times in chip, not necessarily your browser's local time.
End The date and time the pause ends; for a repeating window, only the time of day. The paused checks resume their normal schedule at this time, in the Times in timezone. A repeating window whose end is earlier than its start ends the next day.
Recurrence Shows whether the window repeats or runs once. One Time means the window runs only once between the listed Start and End and does not recur. Daily, Weekly, and Monthly windows repeat at the listed times every day, on the chosen weekdays, or on the chosen days of the month.
Reason A free-text note explaining why the window was scheduled. If the text ends in an ellipsis, open Edit on that row to read the full reason.
Actions Holds the row-level Edit and Delete controls for that maintenance window. The pencil icon opens the window for editing; the trash icon opens a delete confirmation.

Controls reference

New Window

Opens the New Maintenance Window dialog to define a new maintenance window. The button shows for every role; saving a window needs permission to manage maintenance windows.

When to use: Use before a planned infrastructure change, for example scheduling a window named Octans quarter-close burst ahead of a known deployment freeze.

Side effects: Opening the dialog is read-only; confirming inside it with Create adds a new row to the table. Create stays disabled until the window has a name and, for a Weekly or Monthly window, at least one day.

Edit

Opens the Edit Maintenance Window dialog pre-filled with the selected window's current Name, Reason, Recurrence, Start, End, and Affected Checks.

When to use: Use when the planned timing, scope, or reason for an existing window has changed.

Side effects: Opening the dialog is read-only; saving inside it with Save Changes updates the row in place.

Delete

Opens a Delete Maintenance Window confirmation prompt for the selected row.

When to use: Use when a planned outage was cancelled or the window was created in error.

Side effects: Mutating once confirmed: the window is permanently removed and the checks it covered resume their normal schedule immediately.

Verify the result

The Maintenance Windows table lists one row per scheduled window, each showing the checks it pauses, its Start and End time in the appliance's configured timezone, its recurrence, and a reason. After creating or editing a window, the row reflects the saved values; after deleting one, the row disappears, and if it was the last window the table switches to the No maintenance windows state. If a check still generates alerts during a window you scheduled, open the window with Edit to confirm it covers that check, and check that the current time falls between Start and End in the Times in timezone.

Troubleshooting

  • Symptom: The Reason column is cut off with an ellipsis. Fix: Select Edit on that row to read the full reason text.
  • Symptom: A window's Start or End time looks wrong compared to your local clock. Fix: Check the Times in chip; the columns render in the appliance's configured timezone, not your browser's local time.
  • Symptom: The table shows No maintenance windows. Fix: Select New Window to schedule one before the planned downtime begins.
  • Symptom: Saving a window fails with an error. Fix: Confirm your account has permission to manage uptime maintenance windows; ask an administrator to grant it if needed.
  • Symptom: A check still raised an incident during a scheduled window. Fix: Reopen the window with Edit and confirm the Checks scope includes that check and the Start/End range actually covers the incident time. An incident that opened before the window started stays open through it and closes on the first passing run after the window.
Was this article helpful?
0 out of 0 found this helpful