Page 1 of 1

Windows drive monitoring

Posted: Tue May 26, 2015 7:46 am
by maddev
Hi,

I have nsclient running on my windows machines; I would like to monitor all my drives using a single service. Is this possible?
I was able to do this for linux machines using check_nrpe. Not sure of the check command to be used and arguments to be given and config files if any to be modified to achieve this on windows. any guidance will help.

Re: Windows drive monitoring

Posted: Tue May 26, 2015 9:02 am
by jdalrymple
I do this using nsclient and the nrpe_server module with the following command:

Code: Select all

check_nrpe -H <winhost> -c check_drivesize -a "filter=type = 'fixed' and drive regexp '.*[C-Z].*'"
If you don't like the defaults you can append something like:

Code: Select all

MaxWarn=80% MaxCrit=90%

Re: Windows drive monitoring

Posted: Wed May 27, 2015 7:04 pm
by Box293
I have some more detailed examples here:

http://sites.box293.com/nagios/guides/c ... disk-usage

Re: Windows drive monitoring

Posted: Thu May 28, 2015 2:18 am
by maddev
anyway to achieve this using nsclient plugin check_xi_service_nsclient; I really cant get them to open up nrpe ports from windows machines.

Re: Windows drive monitoring

Posted: Thu May 28, 2015 9:21 am
by jdalrymple
No, not easily.

My advice - start fighting the NRPE battle today. Module nsclientserver will not see any further development ever, not on the client side Nagios, not on the server side. If you're happy monitoring what you can today and will never want to monitor anything else (and don't mind specifying drive letters individually) ... check_nt is for you. If you want to open yourself to the world of endless monitoring on Windows systems, plan on doing it over 5666.

Re: Windows drive monitoring

Posted: Thu May 28, 2015 5:05 pm
by Box293
You *could* configure the NSClient++ NRPE module to run on port 12489 AND disable the check_nt module and perform check_nrpe requests over port 12489. Will require you to change the commands that your services use, reconfigure all of your services and all your historical data will probably become incompatible.

This is a bit of work here and ultimately I can see it causing you more troubleshooting headaches in the future.