-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Nagstamon shouldn't report administratively down hosts (and associated services) #986
Comments
|
So the true output in my situation should be "1 DOWN | 1 CRITICAL | 2 WARNING". |
Did you apply some filtering in Nagstamon? Did you try with latest testing release? |
Thanks. "Missed" the filter tab. I see it now. Though not sure if the "All down hosts" filter applies to both "Administratively" downed hosts and hosts that actually went down? I would prefer to filter out only hosts I intentionally put down, not ones with actually issues. |
Hi @ami5451, Which monitoring server of which version and Nagstamon version do you use? |
Hi HenriWahl, 3.12.0. I also noticed, it doesn't keep the sound (notifications) settings. I have to go into settings and turn it off every time I launch Nagstamon. Thanks. |
@ami5451 if the original issue is fixed now please open new ones for the other issues as it is not easy to track them with non-matching titles and contents. |
I have Nagstamon v3.12.0 installed on my Windows Desktop.
The text was updated successfully, but these errors were encountered: