Host warning state?

[nagios at cooldarkplace.org]

>What"s your goal in doing this?  One thing you can do is add a service_d
>and use the check_cluster plugin so that service_d will be warning if
any >of the other services aren"t ok.

>Nagios is designed to be able to try to figure out if its a service or
host >problem and notify the proper person.  It can be very powerful when
used >that way, and what you suggest goes against that.  I"m having a
hard time >figuring out what your intent could be that would make you
want the hosts >to have a warning state.

What would be really cool would be a variable either in the main
nagios.cfg or a per host variable like: host_warn_on_service_failure=0 or
1.  There may in fact be a way to do something like this already, but I
haven't been able to find it in the documentation or 2 months of mailing
list archives.


I suspect his goal here(and I have a similar one), is that quite often the
same person or persons who maintains the host itself is also responsible
for the services, especially in smaller shops.  In this situation, it
makes a good amount of sense.  If I have 10 services on every machine, and
I'm responsible for both the host and service states of all of them, why
not have service failure trigger some sort of host notification rather
than defining notifications and escalations for each service on the
machine?

Imagine 4 admins managing 40 or so hosts.  Each of the 4 admins has 10
hosts and associated services as their "primary" responsibilty.  Another
10 hosts and associated services as their "secondary"
responsibilty(covering in the event that the primary doesn't respond fast
enough) and also needs to know if any of the other 20 hosts have been
misbehaving for quite some time now(meaning neither the primary or
secondary has acknowledged/addressed the problem).

I am in such a situation right now.  All my host escalations have been
configured based on a chain similar to that above, and now I'm faced with
configuring 10 times as many service escalations, all of which have rules
identical to the service escalations.  Forgetting the amount of work it
represents for a moment, its going to make the config files a lot more
unmanageable and simultaneously eat up 10 times more memory.

I'm considering writing some sort of shell script to walk through my
services file, scooping up all the services, and then using the host
escalations I've already defined as a template to write out a gigantic
escalations.cfg, but there would be so much redundant information in there
even if I use massive templating, it seems like there has to be an easier
way.

Any ideas greatly appreciated!

  Thanks,
   -Tony





-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null