NSClient++ Help (#1) - CheckServiceState & Acknowledgement (#1030) - Message List
Hello,
I post this message here because i don't know if it's normal, a bug or a feature request:
In my company i have configured a check for Windows Services that are set to automatically but not started. So when an automatically service isn't started a critical message is showing. That's ok. But if i acknowledge this message and a second service is getting stopped this acknowledged message isn't showing up again. But for me it would be important that every new services that is getting stopped show up again (disacknowledge again on every new service stop).
So it's a bug or a feature request?
Thanks in advance for your answer.
P.S. to give some technical informations: on my network there are Windows 2003, Windows 2008 and Windows 2008 R2 servers and i use the NSClient++ 0.3.9 (both x32 & x64). And the NSClient++ command is like " $USER1$/check_nrpe -H $HOSTADDRESS$ -c CheckServiceState -a CheckAll? $ARG1$"
-
Message #2724
That would be a feature request. But not sure if it possible since the reported value is "processed by nagios/icinga" so seems like something nagios/icinga should "understand and process" the changed state. But I am doubtful if it does. I would send his of no the nagios/icinga mail list and see if there is a solution.
I guess an option would be to add performance data since then you could graph it :) But that would only show the degrading state so it would miss a service being replaced...
But ask the nagios/icinga people and let me know if there is anything I can do to help nagios/icinga better understand that the situation is now "worse"...
On second though this could actually be solved pretty easily using a lua/pythons script if you had two checks (virtual) which run the same check internally and having the second report failure only if the state changes?
ie.
check_nrpe ... check_primary_failure ... check_nrpe ... check_seconday_failure
Then have seconday_Failure only report errors if state worsen? Let me know if it makes sence I could probably write a sample script for it...
Michael Medin
mickem08/10/12 11:31:34 (10 months ago)-
Message #2733
Hello Mike,
Much thanks for your answer! Nice!
I've sent Nagios a mail and we will wait for answer.
BTW here the sent mail (for historic):
Hello Nagios-Team,
I asked the NSClient++ team for help about a "CheckServiceState" command but they sayd that the value came from Nagios and not from the NSCLient++. So my request/question: Actually when a "Automatic" service is stopped, then Nagios alert me that the service named XYZ is critical. If a second service is in the same state it would be added to the first one without setting a new alert. That is my problem. The for me searched notification is that every stopped service is signaled again. So if i acknowledge one and a new one came up the first acknowledged notification came up in critical state again. What is the easiest way to do this?
Thanks in advance for your answer.
Michael
Mommo33308/22/12 15:40:09 (9 months ago)
-
