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

Nagstamon shouldn't report administratively down hosts (and associated services) #986

Open
ami5451 opened this issue Nov 15, 2023 · 8 comments

Comments

@ami5451
Copy link

ami5451 commented Nov 15, 2023

I have Nagstamon v3.12.0 installed on my Windows Desktop.

@ami5451
Copy link
Author

ami5451 commented Nov 16, 2023

Nagstamon is reporting "7 DOWN, 13 CRITICAL, 2 WARNING". The warning is correct but the other 2 are invalid:
image

@ami5451
Copy link
Author

ami5451 commented Nov 16, 2023

  1. Figured out that Nagstamon is adding systems "In downtime" and systems that are "Down" to get the reported "7 DOWN". But I put those 6 in downtime intentionally so I think they should not be reported by Nagstamon.
  2. The CRITICAL is coming from the "Check_MK" and "Check_MK Discovery" services on the 6x hosts I intentionally put in downtime. Making 12 plus the 1 host that is truly down, making 13. I think the logic needs to be updated so Nagstamon does not report systems (and associated Check_MK/"Check_MK Discovery" services) that are administratively put in downtime. Thank you.

@ami5451
Copy link
Author

ami5451 commented Nov 16, 2023

So the true output in my situation should be "1 DOWN | 1 CRITICAL | 2 WARNING".

@ami5451 ami5451 changed the title Nagstamon Status is OK even though I have at least two services in WARN status Nagstamon shouldn't report administratively down hosts (and associated services) Nov 16, 2023
@HenriWahl
Copy link
Owner

Did you apply some filtering in Nagstamon? Did you try with latest testing release?

@ami5451
Copy link
Author

ami5451 commented Dec 4, 2023

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.
Something not quite related, it seems Nagstamon doesn't auto-reconnect if there is a network issue? It goes to "connection timeout", stays there, and even after the network is restored, one has to go in and use the "Authenticate" option to get it to re-establish connection. This is not much of an issue with the "Floating statusbar", Window or Fullscreen display options, but may be easily missed when using the "Icon in systray" option. Apologies if I am missing something. Thanks.

@HenriWahl
Copy link
Owner

Hi @ami5451,

Which monitoring server of which version and Nagstamon version do you use?

@ami5451
Copy link
Author

ami5451 commented Feb 9, 2024

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.

@HenriWahl
Copy link
Owner

@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.

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

No branches or pull requests

2 participants