Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Resolved Alerts are triggered after exiting maintenance mode #1849

2 tasks
joeldeteves opened this issue Apr 18, 2024 · 3 comments
2 tasks


Copy link

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 --insecure flag 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:

  1. Put a client in maintenance mode
  2. Trigger a reboot
  3. Exit maintenance mode (can be an hour later, it still does it)
  4. "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.


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.

Copy link

can you paste screenshots of your alert policy settings just so I make sure I am replicating the issue properly

Copy link
Contributor Author

Here you go:


Copy link

wh1te909 commented Jun 7, 2024

Fixed in e6225ad will be in next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants