Alerts and reports · 3 of 4
Maintenance windows
Daily windows when a host is expected to go down, such as a nightly reboot or backup, so nobody is woken for it. Problems still there when the window closes alert as usual.
A host that reboots every night at 04:00 shouldn't page anyone at 04:00. A maintenance window holds its alerts while it's expected to be down.
Add windows under Configure › Alerts: a name, the hosts, a daily start time, a time zone and how long it lasts.
What a window does
While a window is open, for the hosts it names:
- problems don't open or fire incidents,
- incidents already open stay as they are: no repeats, and no "resolved" while the host reboots.
When it closes, everything is judged as usual, so a host that's still down then alerts.
Only conditions that belong to a host are held. Checks of sites, mail and DNS aren't: a website down is down, whoever's rebooting. A window may name a cluster, which holds everything about that cluster.
Use the host's own time zone, so daylight saving moves the window with the host's timer.
In the config file
Writing maintenance in obs-beacond.yaml, even as maintenance: [], makes
the file the place for windows:
maintenance:
- name: nightly reboot
hosts: [web1, web2, db1]
daily: "04:00"
timezone: Europe/Berlin # default UTC
duration: 20m
For obs-beacond's own host, the same format goes in a watching agent's
watch_server.quiet (Who watches the server).