In this case we'll have to manually edit resources for dozens of active/passive clusters when active nodes are changing. Something we are trying to avoid by configuring node-independent services.ssax wrote: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).
Monitoring Microsoft Clusters
Re: Monitoring Microsoft Clusters
Re: Monitoring Microsoft Clusters
What you could do then is just setup one through the wizard and then use Configure > Core Config Manager > Bulk Host Cloning and Import wizard to clone it to the ones you import.
OR
You can add all the generic services manually (or use the wizard and remove the single host and change the config name) and attach them to a hostgroup and then add the hosts to the hostgroup and they will automatically receive it.
If this is not what you are looking for, let me know.
Thank you
OR
You can add all the generic services manually (or use the wizard and remove the single host and change the config name) and attach them to a hostgroup and then add the hosts to the hostgroup and they will automatically receive it.
If this is not what you are looking for, let me know.
Thank you
Re: Monitoring Microsoft Clusters
Let's start from scratch with recent Client install
- where to define External Script (check_mscs=cscript.exe //T:30 //NoLogo scripts\check_microsoft_cluster.vbs $ARG1$ $ARG2$)?
In this case (btw containing 2 arguments, not one)
/Dimitri
- where to define External Script (check_mscs=cscript.exe //T:30 //NoLogo scripts\check_microsoft_cluster.vbs $ARG1$ $ARG2$)?
In this case (btw containing 2 arguments, not one)
/Dimitri
You do not have the required permissions to view the files attached to this post.
Re: Monitoring Microsoft Clusters
This is a misunderstanding, absolutely not what we need (we need fully automated monitoring of cluster resources with respect to active/passive nodes change)ssax wrote:What you could do then is just setup one through the wizard and then use Configure > Core Config Manager > Bulk Host Cloning and Import wizard to clone it to the ones you import.
OR
You can add all the generic services manually (or use the wizard and remove the single host and change the config name) and attach them to a hostgroup and then add the hosts to the hostgroup and they will automatically receive it.
If this is not what you are looking for, let me know.
Thank you
Please look at a post down below: starting all over again
Re: Monitoring Microsoft Clusters
dlukinski wrote:Let's start from scratch with recent Client install
- where to define External Script (check_mscs=cscript.exe //T:30 //NoLogo scripts\check_microsoft_cluster.vbs $ARG1$ $ARG2$)?
In this case (btw containing 2 arguments, not one)
/Dimitri
In your nsclient.ini, under [/settings/external scripts/alias], add below that -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.
Code: Select all
check_mscs=cscript.exe //T:30 //NoLogo scripts\check_mscs.vbs $ARG1$
Code: Select all
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscs -a $ARG1$
Former Nagios Employee
Re: Monitoring Microsoft Clusters
rkennedy wrote:dlukinski wrote:Let's start from scratch with recent Client install
- where to define External Script (check_mscs=cscript.exe //T:30 //NoLogo scripts\check_microsoft_cluster.vbs $ARG1$ $ARG2$)?
In this case (btw containing 2 arguments, not one)
/DimitriFor 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.
[/qupte]
In your nsclient.ini, under [/settings/external scripts/alias], add below that -From there, you will need to create a command definition for NRPE (I think you did this with check_mscs_nrpe, so modify this one). Modify the command line to be like so -Code: Select all
check_mscs=cscript.exe //T:30 //NoLogo scripts\check_mscs.vbs $ARG1$Once that is done, modify the service definition to use $ARG1$ ONLY. The plugin supports two things, RES and NODE. Set your $ARG1$ to "RES Disk R:,Disk S:" for example, and it should work at that point.Code: Select all
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscs -a $ARG1$
Could it be us talking about different version of the script (attached what I got from Nagios Exchange - 2 arguments mentioned and so is in the README)?
You do not have the required permissions to view the files attached to this post.
Re: Monitoring Microsoft Clusters
Heh - yeah, looks like that's the case. Their is another script called check_mscs. The one I was referencing is https://exchange.nagios.org/directory/P ... bs/details
I believe this is the one you're refering to - https://exchange.nagios.org/directory/P ... pt/details
As this is the case, here's new instructions. I renamed it from check_mscs to check_mscluster.
Add the file check_microsoft_cluster.vbs to your scripts folder located where NSClient is installed.
Modify the NSClient configuration file, and add this line -
In Nagios, modify your check_mscs_nrpe command from the Core Config Manager. Change the command line to this -
Once that is done, modify the service definition to use $ARG1$ and $ARG2$ only, based on the variables that the script uses.
At that point you should be able to use the plugin as expected.
I believe this is the one you're refering to - https://exchange.nagios.org/directory/P ... pt/details
As this is the case, here's new instructions. I renamed it from check_mscs to check_mscluster.
Add the file check_microsoft_cluster.vbs to your scripts folder located where NSClient is installed.
Modify the NSClient configuration file, and add this line -
Code: Select all
check_mscluster=cscript.exe scripts\check_microsoft_cluster.vbs $ARG1$
Code: Select all
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscluster -a "$ARG1$" "$ARG2$"
At that point you should be able to use the plugin as expected.
Former Nagios Employee
Re: Monitoring Microsoft Clusters
Check returns "Unknown command(s): check_mscluster" - Sorry, can't figure what I am still missing.rkennedy wrote:Heh - yeah, looks like that's the case. Their is another script called check_mscs. The one I was referencing is https://exchange.nagios.org/directory/P ... bs/details
I believe this is the one you're refering to - https://exchange.nagios.org/directory/P ... pt/details
As this is the case, here's new instructions. I renamed it from check_mscs to check_mscluster.
Add the file check_microsoft_cluster.vbs to your scripts folder located where NSClient is installed.
Modify the NSClient configuration file, and add this line -In Nagios, modify your check_mscs_nrpe command from the Core Config Manager. Change the command line to this -Code: Select all
check_mscluster=cscript.exe scripts\check_microsoft_cluster.vbs $ARG1$Once that is done, modify the service definition to use $ARG1$ and $ARG2$ only, based on the variables that the script uses.Code: Select all
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscluster -a "$ARG1$" "$ARG2$"
At that point you should be able to use the plugin as expected.
Re: Monitoring Microsoft Clusters
dlukinski wrote:rkennedy wrote:Heh - yeah, looks like that's the case. Their is another script called check_mscs. The one I was referencing is https://exchange.nagios.org/directory/P ... bs/details
I believe this is the one you're refering to - https://exchange.nagios.org/directory/P ... pt/details
As this is the case, here's new instructions. I renamed it from check_mscs to check_mscluster.
Add the file check_microsoft_cluster.vbs to your scripts folder located where NSClient is installed.
Modify the NSClient configuration file, and add this line -In Nagios, modify your check_mscs_nrpe command from the Core Config Manager. Change the command line to this -Code: Select all
check_mscluster=cscript.exe scripts\check_microsoft_cluster.vbs $ARG1$Once that is done, modify the service definition to use $ARG1$ and $ARG2$ only, based on the variables that the script uses.Code: Select all
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscluster -a "$ARG1$" "$ARG2$"
At that point you should be able to use the plugin as expected.
Re: Monitoring Microsoft Clusters
Getting error: "Unknown command(s): check_mscluster"dlukinski wrote:dlukinski wrote:rkennedy wrote:Heh - yeah, looks like that's the case. Their is another script called check_mscs. The one I was referencing is https://exchange.nagios.org/directory/P ... bs/details
I believe this is the one you're refering to - https://exchange.nagios.org/directory/P ... pt/details
As this is the case, here's new instructions. I renamed it from check_mscs to check_mscluster.
Add the file check_microsoft_cluster.vbs to your scripts folder located where NSClient is installed.
Modify the NSClient configuration file, and add this line -In Nagios, modify your check_mscs_nrpe command from the Core Config Manager. Change the command line to this -Code: Select all
check_mscluster=cscript.exe scripts\check_microsoft_cluster.vbs $ARG1$Once that is done, modify the service definition to use $ARG1$ and $ARG2$ only, based on the variables that the script uses.Code: Select all
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 30 -c check_mscluster -a "$ARG1$" "$ARG2$"
At that point you should be able to use the plugin as expected.
- Where exactly we define the script in nsclient.ini file?
/Dimitri