[BUG]: Resolved Alerts are triggered after exiting maintenance mode
joeldeteves opened this issue · comments
Server Info (please complete the following information):
- OS: Debian (Kubernetes Node)
- Browser: Chrome / Edge
- RMM Version (as shown in top left of web UI): v0.18.2
Installation Method:
- Standard
- Standard with
--insecureflag at install - [ x ] Docker
Agent Info (please complete the following information):
- Agent version (as shown in the 'Summary' tab of the agent from web UI): v2.7.0
- Agent OS: [e.g. Win 10 v2004, Server 2016] Windows Server 2019 Standard
Describe the bug
It seems like whenever we turn off maintenance mode we get a ton of “resolved” alerts.
We don’t get alerted during the window which is correct, but we get alerted for service restorations after the window is over, even if those services were resolved during the window.
This has been going on for as long as I remember, I just haven't had time to open an issue for it. I am confident every version of Tactical has done this, at least in our specific environment.
To Reproduce
Steps to reproduce the behavior:
- Put a client in maintenance mode
- Trigger a reboot
- Exit maintenance mode (can be an hour later, it still does it)
- "Service Check: Resolved" gets triggered even though the service was started long before exiting maintenance mode
Expected behavior
Maintenance mode should not trigger Resolved alerts after exiting maintenance mode.
Screenshots
N/A
Additional context
@wh1te909 is familiar with our environment. It is technically "unsupported" but nonetheless if it's something on our side, just need to know what the cause is so we can address and resolve accordingly. I am filing it as a bug report for now per conversation on Discord.
can you paste screenshots of your alert policy settings just so I make sure I am replicating the issue properly
Here you go:
