-
-
Notifications
You must be signed in to change notification settings - Fork 437
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
Comments
can you paste screenshots of your alert policy settings just so I make sure I am replicating the issue properly |
wh1te909
added a commit
to sadnub/tacticalrmm
that referenced
this issue
Jun 7, 2024
Fixed in e6225ad will be in next release |
wh1te909
added a commit
to sadnub/tacticalrmm
that referenced
this issue
Jun 8, 2024
wh1te909
added a commit
to sadnub/tacticalrmm
that referenced
this issue
Jun 11, 2024
wh1te909
added a commit
to sadnub/tacticalrmm
that referenced
this issue
Jun 19, 2024
1 task
wh1te909
added a commit
to sadnub/tacticalrmm
that referenced
this issue
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Server Info (please complete the following information):
Installation Method:
--insecure
flag at installAgent Info (please complete the following information):
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:
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.
The text was updated successfully, but these errors were encountered: