Propagating Service Changes

[Mohr James]

Servus Matthias!

Thanks for that tip. It looks really interesting and exciting. We currently have Nagios 2, but have 3 on a test system and probably won't be making any major changes until we have 3 up and running. I'll get it going on the test system and see how it works. Thanks again!

Gruß aus Coburg,

Jim Mohr

> -----Ursprüngliche Nachricht-----
> Von: Matthias.Flacke at gmx.de [mailto:Matthias.Flacke at gmx.de] 
> Gesendet: Mittwoch, 2. Januar 2008 14:21
> An: Mohr James; nagios-users at lists.sourceforge.net
> Betreff: Re: [Nagios-users] Propagating Service Changes
> 
> 
> Maybe you can solve your issue already on the plugin level:
> 
> - If you want to evaluate the state of existing Nagios 
> services take a look onto check_cluster.
> 
> - If you want to cover more sophisticated setups and be able 
> to do a fine granulated evaluation of the results of your 
> child checks you can also take check_multi 
> (http://www.my-plugin.de/wiki/projects/check_multi/start) , 
> which is mainly written for Nagios 3, but also works with Nagios 2.
> The state evaluation topic is handled in the 'Process Views' 
> page (http://www.my-plugin.de/wiki/projects/check_multi/process_views)
> 
> HTH - Matthias Flacke
>  
> ----- original message --------
> 
> Subject: [Nagios-users] Propagating Service Changes
> Sent: Wed, 02 Jan 2008
> From: Mohr James<james.mohr at elaxy.com>
> 
> > Hi All!
> > 
> > First off my apologies. Apparently I forget to stop the 
> subscription 
> > while I was on vacation, so I would imagine that most 
> everyone got a 
> > vacation notice from me. Sorry!
> > 
> > We have a situation (using Nagios 2.5) we need to monitor/report 
> > services "conceptually". That is, we have several services that are 
> > monitored and only when all of these are not accessible do 
> we report 
> > that the main service is not accessible. I couldn't find any 
> > information on propagating services, so I was thinking 
> about using an 
> > event handler that would run whenever one of the low-level services 
> > changes state. The handler would then check the other services 
> > (perhaps using the Nagios-Object perl module) and if all of 
> the other 
> > services are critical, the handler would use send_nsca to send a 
> > message to the master service. However, if there is some mechanism 
> > already built in (even Nagios 3.0) that would save me the 
> work of re-inventing the wheel.
> > 
> > I would be grateful for any input or ideas.
> > 
> > Regards,
> > 
> > Jim Mohr
> > 
> > 
> ----------------------------------------------------------------------
> > --- This SF.net email is sponsored by: Microsoft Defy all 
> challenges. 
> > Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > 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
> > 
> > 
> 
> --- original message end ----
> 
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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