Maintenance windows
Nexus Telemetry Fleet has 3 ways to stop alerts about something already known. A maintenance window covers planned work on a terminal or a group. An acknowledgement records that someone has seen an alert. A silence stops a terminal’s alerts for a set time. Alerts are sent by the fleet server, by email or webhook. See Alerts for the alerts and Users and roles for the roles named below.
Terminal maintenance
A maintenance window is scheduled before planned work on a terminal. During the window the fleet server sends no alert email about the terminal. A webhook is still posted, with the reason. Users with the Owner, Admin or Operator role can schedule one. The controls are under Alerts and maintenance on the Admin view of the terminal’s page.
- Press Schedule maintenance.
- Set Start to Now, or to At a time with a Start time (UTC).
- Choose a Duration: 30 min, 1h, 2h, 4h, 8h, 12h or 1d. The default is 4h.
- Type a Reason (optional) and press Start maintenance.
Start time (UTC) is read as UTC, not as local time.
A window in progress is listed under Maintenance with End maintenance early. A window scheduled for later is listed with Cancel. When the terminal’s group is in maintenance, the terminal’s window is marked via group, and it is ended from the group.
Group maintenance
A group’s maintenance window covers every terminal in the group. Users with the Owner or Admin role can schedule one. Users with the Operator or Viewer role cannot.
- Open Manage groups from the Groups view.
- Open the group’s actions menu and choose Schedule maintenance.
- Set Start, Duration and Reason (optional) as for a terminal.
- Press Start maintenance. For a window that starts later, the button reads Schedule maintenance.
Once a window is scheduled, the menu offers Change scheduled maintenance and Cancel scheduled maintenance. While a window is open, it offers End maintenance early. A change that fails part way leaves the old window in place.
Acknowledge
An acknowledgement records that someone has seen an alert. Acknowledge is beside each open alert under Alerts and maintenance on the Admin view of the terminal’s page. The alert then shows the name of the user who acknowledged it. Users with the Owner, Admin or Operator role can acknowledge.
Silence
A silence stops a terminal’s alerts for a set time. Users with the Owner, Admin or Operator role can set one. Silence… is under Alerts and maintenance on the Admin view of the terminal’s page, and takes 3 fields.
| Field | Takes |
|---|---|
| Silence | All alerts, or one kind: Offline, Service restricted or On backup. See Alerts for the kinds |
| For | 1h, 6h, 1d, 3d, 7d or 30d. The default is 1d |
| Reason (optional) | Free text, kept for the record |
A silence always has an end time, and 30 days is the longest. The fleet server sends no alert email for the terminal while the silence lasts, and posts the webhook with the reason. Unsilence, on the Alerts view of the terminal’s page, ends it early.
Effect of each control
| Control | Alerts | Availability report |
|---|---|---|
| Maintenance window | No email is sent for the terminals in the window. The webhook is still posted | Down time inside the window is counted as Planned |
| Acknowledge | No further email is sent for the alert. The webhook is still sent | No effect |
| Silence | No email is sent for the terminal until the silence ends. The webhook is still posted | No effect |
A maintenance window does not remove down time from the Availability report. It marks the down time as planned rather than unplanned. An acknowledgement or a silence changes nothing the dashboard shows. A terminal that is down inside a maintenance window reads Planned outage in place of Outage.
Badges and the paused list
| Where | Shows |
|---|---|
| The terminal’s Live view | A Maintenance badge during a window. A Silenced badge during a silence |
| The group’s card on the Groups view | A Maintenance badge during the group’s window |
| The Status view | Planned outage in place of Outage for a terminal that is down during a window |
| Alerts currently paused on the Alerts page | Every maintenance window in the organisation, open or scheduled, with Scope, Status (Paused now or Scheduled), Until, Reason, By, and End early or Cancel |
When the fleet server restarts a terminal’s collector for a software update, it schedules a window for the restart, so the restart raises no alert. A collector stopped by hand has no window, and an offline alert is sent with the cause stopped at the terminal. See Release channels for updates.
A notice to every user about maintenance on the fleet server itself is separate. It is posted under Maintenance notice on the Settings page.