1. Make sure that you are monitoring the services (PING in this example) on all servers (you can disable notifications for them, this is important so you don't get notifications when they are down), these service checks are what will be used by the check_cluster plugin and need to exist.
2. Create a new command:
- Command Name: check_service_cluster
- Command Line: $USER1$/check_cluster --service -l $ARG1$ -w $ARG2$ -c $ARG3$ -d '$ARG4$'
- Command Type: check command
3. Create the service cluster check:
- Description: PING_Cluster
- Check command: check_service_cluster
- $ARG1$: PING_Cluster
- $ARG2$: 3 <- Set this to one MORE than your total number of services (2 services + 1 = 3) - We don't care about warnings in this example
- $ARG3$: 1 <- Set this to one LESS than your total number of services (2 services - 1 = 1)
- $ARG4$: $SERVICESTATEID:yourhost1:PING$,$SERVICESTATEID:yourhost2:PING$
NOTE: The hostname and the service description in $ARG4$ need to be exact (case sensitive).
The way this would work is that whenever that service is not running on ANY of the nodes it would generate a CRITICAL. So the check_cluster uses the statuses of all of each individual service checks to determine if there is an issue and since you disabled the notifications on the individual services you won't get those notifications, this is the service that will do the notifying.
Please read here for more information:
https://assets.nagios.com/downloads/nag ... sters.html
Here are some other Microsoft Cluster plugins that I found as well:
https://exchange.nagios.org/index.php?o ... %20cluster