Page 2 of 5
Re: Monitoring Microsoft Clusters
Posted: Mon Nov 23, 2015 3:22 pm
by rkennedy
I'll leave this thread open for now then, please respond to it once we've finished working through NRPE and we will proceed at that point.
Re: Monitoring Microsoft Clusters
Posted: Mon Nov 30, 2015 11:37 am
by dlukinski
rkennedy wrote:I'll leave this thread open for now then, please respond to it once we've finished working through NRPE and we will proceed at that point.
Hello again
Your Script-based cluster check started to work now (I used newer client)
What is the best practice for configuring services to be monitored? (Resources like DISK, CPU, RAM and windows services)?
Thank you
Re: Monitoring Microsoft Clusters
Posted: Mon Nov 30, 2015 12:10 pm
by hsmith
dlukinski wrote:What is the best practice for configuring services to be monitored? (Resources like DISK, CPU, RAM and windows services)?
It is all pretty situational. Have you tried using the Windows Server Configuration Wizard? It can set up a lot of this for you with minimal complexity.
Re: Monitoring Microsoft Clusters
Posted: Tue Dec 01, 2015 4:11 pm
by dlukinski
hsmith wrote:dlukinski wrote:What is the best practice for configuring services to be monitored? (Resources like DISK, CPU, RAM and windows services)?
It is all pretty situational. Have you tried using the Windows Server Configuration Wizard? It can set up a lot of this for you with minimal complexity.
I rushed to conclusions a bit
Script checks are clearly green and OK, however Status information produced is always the same: "I (0.3.9.328 2011-08-16) seem to be doing fine..."
- no matter if CLRES or CLNODE is used
Re: Monitoring Microsoft Clusters
Posted: Tue Dec 01, 2015 4:25 pm
by rkennedy
What is the check_command being used for that? Can you provide a screenshot?
Re: Monitoring Microsoft Clusters
Posted: Tue Dec 01, 2015 5:19 pm
by dlukinski
rkennedy wrote:What is the check_command being used for that? Can you provide a screenshot?
Re: Monitoring Microsoft Clusters
Posted: Wed Dec 02, 2015 1:15 pm
by lmiltchev
This is a 3rd party plugin, and I am not familiar with it, but according to the usage, you need to pass only one argument:
VBScript to check MSCS ressources via NRPE (NSClient++ with NRPE Listener)
##########################################################################
Usage:
+++++
For use with NSClient++ please add the following line to your NSC.INI [NRPE Handlers]:
check_mscs=cscript.exe //T:30 //NoLogo scripts\check_mscs.vbs $ARG1$
and copy "check_mscs.vbs" into "scripts\" folder at each node. Refer to NSClient++ Documentation for using remote checks via NRPE.
###command definition###
define command {
command_name check_mscs
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscs -a $ARG1$
}
###service definition###
define service{
use generic-service
host_name MSCSSVC01
service_description MSCS Ressources
process_perf_data 0
check_command check_mscs!"RES Disk R:,Disk S:"
}
Please remember to point this check to the corresponding clustered ressource (type "network name" & "ip address") - not to a single node. (Of course you can use other methods, i.e. check_cluster)
What it does:
+++++++++++++
The plugin will accept the following parameters:
check_mscs.vbs RES [ressource list]
check_mscs.vbs NODE [node list]
...
You are passing two args. Can you try modifying your command according to the documentation (use one arg), run your check from the command line and show the output?
Re: Monitoring Microsoft Clusters
Posted: Mon Dec 14, 2015 10:14 am
by dlukinski
lmiltchev wrote:This is a 3rd party plugin, and I am not familiar with it, but according to the usage, you need to pass only one argument:
VBScript to check MSCS ressources via NRPE (NSClient++ with NRPE Listener)
##########################################################################
Usage:
+++++
For use with NSClient++ please add the following line to your NSC.INI [NRPE Handlers]:
check_mscs=cscript.exe //T:30 //NoLogo scripts\check_mscs.vbs $ARG1$
and copy "check_mscs.vbs" into "scripts\" folder at each node. Refer to NSClient++ Documentation for using remote checks via NRPE.
###command definition###
define command {
command_name check_mscs
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscs -a $ARG1$
}
###service definition###
define service{
use generic-service
host_name MSCSSVC01
service_description MSCS Ressources
process_perf_data 0
check_command check_mscs!"RES Disk R:,Disk S:"
}
Please remember to point this check to the corresponding clustered ressource (type "network name" & "ip address") - not to a single node. (Of course you can use other methods, i.e. check_cluster)
What it does:
+++++++++++++
The plugin will accept the following parameters:
check_mscs.vbs RES [ressource list]
check_mscs.vbs NODE [node list]
...
You are passing two args. Can you try modifying your command according to the documentation (use one arg), run your check from the command line and show the output?
Thank you, Looks like I misunderstood the entire concept.
So I create multiple commands per resource checked?
Could you please give one example of command + resource (CPU?) + service configured?
- anything I try returns this: Could not construct return packet in NRPE handler check client side (nsclient.log) logs...
or that: (No output on stdout) stderr: execvp(check_mscs!, ...) failed. errno is 2: No such file or directory
Re: Monitoring Microsoft Clusters
Posted: Mon Dec 14, 2015 5:33 pm
by hsmith
Can you post your nsc.ini/nsclient.ini here for us to review?
Re: Monitoring Microsoft Clusters
Posted: Mon Dec 14, 2015 5:38 pm
by ssax
What I would do is go to Configure > Configuration Wizards > Windows Server monitoring wizard and setup the default checks for each node for the generic stuff like CPU/MEM/Users/etc because you'll want to monitor that on all the nodes anyways, then you can add the cluster specific checks with this (or other plugins).