Global Service Dependancies
Posted: Fri May 11, 2012 2:34 pm
What we are trying to do.
We have several situations where we need X_alive checks for all checks that use that protocol.
Examples being an SNMP_Alive check as a dependency for all snmp checks.
JMX_Alive for all JMV checks using JMX.
NRPE_Alive... you get the idea.
We can do service dependancies for each host, with the SNMP Checks on that box, and the SNMP_Alive check as the master service.
But this requires us to set up a service dependency for EVERY box that uses SNMP.
Thus making dependency management unmanageable.
Is there a way to say ANY host with checks SNMP_xxx will depend on SNMP_Alive on the same host.
This would make it so we could define that all checks we select are SNMP based, and thus, would have an SNMP_Alive dependency (which of course would have to exist on the host as well)
POSSIBLE BUG:
When we were testing this. The notes for Dependent hosts(*) states "Leaving this directive blank can be used to create "same host" dependencies." but, we are unable to leave it blank.
It simply errors out saying that a required field is not filled out (and does not say which fields)
We had Hosts, Services, Dependent Services, Period, failure criteria all set.
Any idea would be warmly welcome, as I am not "enthusiastic" about the idea of managing, and needing to remember to add dependancy for any snmp, nrpe, jmx, etc... check that we ever add in the future.
It would be substantially faster to simply add this new JMX check to the list of known JMX checks, and it will have a dependency to JMX_Alive on the same host.
We have several situations where we need X_alive checks for all checks that use that protocol.
Examples being an SNMP_Alive check as a dependency for all snmp checks.
JMX_Alive for all JMV checks using JMX.
NRPE_Alive... you get the idea.
We can do service dependancies for each host, with the SNMP Checks on that box, and the SNMP_Alive check as the master service.
But this requires us to set up a service dependency for EVERY box that uses SNMP.
Thus making dependency management unmanageable.
Is there a way to say ANY host with checks SNMP_xxx will depend on SNMP_Alive on the same host.
This would make it so we could define that all checks we select are SNMP based, and thus, would have an SNMP_Alive dependency (which of course would have to exist on the host as well)
POSSIBLE BUG:
When we were testing this. The notes for Dependent hosts(*) states "Leaving this directive blank can be used to create "same host" dependencies." but, we are unable to leave it blank.
It simply errors out saying that a required field is not filled out (and does not say which fields)
We had Hosts, Services, Dependent Services, Period, failure criteria all set.
Any idea would be warmly welcome, as I am not "enthusiastic" about the idea of managing, and needing to remember to add dependancy for any snmp, nrpe, jmx, etc... check that we ever add in the future.
It would be substantially faster to simply add this new JMX check to the list of known JMX checks, and it will have a dependency to JMX_Alive on the same host.