Q: time-saving tricks for Service Dependencies?

[Carroll, Jim P [Contractor]]

Just looking for some 'warm fuzzies' here.  In:

http://nagios.sourceforge.net/docs/1_0/templatetricks.html

under "Service Dependencies", there appears to be a great time-saver.

However, I'm concerned that creating this definition will mean that *all*
hosts defined in the dependent_host_name declaration would become dependent
on *all* hosts defined in the host_name declaration.

(I have a similar concern when using a
dependent_hostgroup_name/hostgroup_name approach.)

Can anyone say with authority and conviction that (using the example given
on that page) SERVICE2 on HOST3 is dependent on SERVICE2 on HOST1, and
SERVICE2 on HOST4 is dependent on SERVICE2 on HOST2, but that there's no
crossover where SERVICE2 on HOST3 becomes dependent on SERVICE2 on HOST2,
and likewise with SERVICE2 on HOST4 crossing over to SERVICE2 on HOST1?

A 1-to-1 correlation would do quite nicely, so long as there are N hosts
defined on each of the dependent_host_name and host_name lines.  A
1-to-many, many-to-1, or many-to-many is *not* what I want.

In short:  I'd like to take advantage of this time-saving feature, but I
don't want to end up creating logic where a vast selection of services are
dependent on one particular service being up or down.

Thoughts?

jc


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com