Uptime Kuma sends notifications (Telegram) after every maintenance window for monitors that where already down before the maintenance starts.
I have 72 monitors and at any time between 1 and 5 of them can be down from time from time, which is kind of by design. But it's mostly for a night, or a day, and I cannot pause them everytime as I do want to get notified when they do get back up.
Apart from that all monitored devices reboot once every night, which takes about 15 minutes, which is why I have a daily Maintenance window of 30 minutes during the night.
I'm used to Uptime Robot and a maintance window over there means just a full pause on checking/reporting on the monitors. Uptime Kuma seems to be doing it different and sends a notification of monitors being down after maintenance, although these monitors where already down before.
This is undesired behaviour, as it's unclear at first glance if something new has gone down and needs attention, or it's just a monitor known for being down already.
π Reproduction steps
Have one or more monitors that are down beforehand
Plan a recurring maintenance window
Have the same monitors that are down after the window ends
π Expected behavior
In my eyes, nothing should happen as a maintenance window is a full pause and the status of monitors do not change between start and end of the window
π Actual Behavior
Uptime Kuma sends out notifications (Telegram) for the monitors that where down before maintenance and stay down after maintenance.
β οΈ Please verify that this bug has NOT been raised before.
π‘οΈ Security Policy
Description
Uptime Kuma sends notifications (Telegram) after every maintenance window for monitors that where already down before the maintenance starts.
I have 72 monitors and at any time between 1 and 5 of them can be down from time from time, which is kind of by design. But it's mostly for a night, or a day, and I cannot pause them everytime as I do want to get notified when they do get back up.
Apart from that all monitored devices reboot once every night, which takes about 15 minutes, which is why I have a daily Maintenance window of 30 minutes during the night.
I'm used to Uptime Robot and a maintance window over there means just a full pause on checking/reporting on the monitors. Uptime Kuma seems to be doing it different and sends a notification of monitors being down after maintenance, although these monitors where already down before.
This is undesired behaviour, as it's unclear at first glance if something new has gone down and needs attention, or it's just a monitor known for being down already.
π Reproduction steps
π Expected behavior
In my eyes, nothing should happen as a maintenance window is a full pause and the status of monitors do not change between start and end of the window
π Actual Behavior
Uptime Kuma sends out notifications (Telegram) for the monitors that where down before maintenance and stay down after maintenance.
π» Uptime-Kuma Version
1.20.1
π» Operating System and Arch
Ubuntu 22.04.1
π Browser
Firefox 110.0 64-bits
π Docker Version
23.0.1
π© NodeJS Version
No response
π Relevant log output
No response