After move to Check MK and using only Check MK Agent on Windows hosts I would like to have similiar check as it was previous. Using one command
I was able to check is it one or more services on one or more hosts started.
check_nrpe -H $HOSTADDRESS$ -c nsc_checkservicestate -a 'Service1, Service2, Service…n… ’
Also, that was showed up on host as one item – one service check, but if any of defined services is stopped that check goes to critical.
I know that I can use (and I’ve created) rules for services discovery on hosts but that is not suitable because I have to go to any host, services,
and check / turn on twelve services to check on n hosts. Boring J
Sounds like you want to modify the “Windows Service Summary” ruleset.
Enable it, change it from OK to WARN or CRIT, and then start excluding the Windows services that automatically start and stop on their own, so you will only be alerted for service that autostart, and are expected
to stay running continually.
After move to Check MK and using only Check MK Agent on Windows hosts I would like to have similiar check as it was previous. Using one command
I was able to check is it one or more services on one or more hosts started.
check_nrpe -H $HOSTADDRESS$ -c nsc_checkservicestate -a 'Service1, Service2, Service…n… ’
Also, that was showed up on host as one item – one service check, but if any of defined services is stopped that check goes to critical.
I know that I can use (and I’ve created) rules for services discovery on hosts but that is not suitable because I have to go to any host, services,
and check / turn on twelve services to check on n hosts. Boring J