Notifications during maintenance or dependencies

Paused devices and disabled checks do not generate new notifications from regular checks. The same applies to checks suspended by a device dependency. After resuming, they collect their own current results again.

For planned maintenance, you can manually pause the affected devices and then start them again. Previously created and queued notifications remain in place. If their delivery must also be stopped, the respective delivery channel must be disabled under Notifications and saved; this discards its queued notifications.

This version provides no calendar-controlled maintenance windows in the notification form, no reminders for unchanged problems and no escalation to additional recipients after a period of time. The Failure threshold of the respective check delays confirmation of connection or reachability errors. Warning and critical threshold violations that have already been measured can, however, lead to an immediate state change. A check error is not the same as a reachability error in every check method; refer to the result of the relevant check.