AW: Cascading Services/Service hierarchy

[Jaap Hogenberg]

James,

I use the check_cluster service check for services that
are provided by a cluster. I configured it to only show critical
if all nodes in the cluster are critical.
That way your availability reports will be correct.

HTH

Jaap

On Fri, 2004-09-24 at 15:25, Mohr James wrote:
> Servus Gerd!
> 
> Thanks for that kick in the pants. I missed that because I was not really thinking about it in terms of a "dependancy", per se. The biggest issue is that in the OpenView model our services are not tied to a host, more or less virtual. That is, we have services that are dependant on the services on two hosts. If one goes down, then the service is still accessible. Only when both of the bottom-level services go down is the service down. This top-level service is never checked directly, it's just dependant on the other two.
> 
> The real problem is reporting/SLAs. We are required to guarantee the top-level services, but the lower-level services determine if the top-level service is accessible. However, as I said, this is the OpenView model and we really need to keep away from trying to figure out how to "port" OpenView to Nagios. Instead, we need to look at the services we are providing and how we can monitor them with Nagios.
> 
> Danke and Greetings from Coburg!
> 
> James Mohr
> 
> -----Ursprüngliche Nachricht-----
> Von: Gerd Müller [mailto:gmueller at netways.de] 
> Gesendet: Freitag, 24. September 2004 14:49
> An: Mohr James
> Cc: Nagios-users at lists.sourceforge.net
> Betreff: Re: [Nagios-users] Cascading Services/Service hierarchy
> 
> 
> Hi James,
> 
> have a look at "Host and Service Dependencies" 
> 
> Gerd
> 
> Am Fr, den 24.09.2004 schrieb Mohr James um 14:25:
> > Hi All!
> > 
> > Is there any way to cascade services? That is, services that contain 
> > other services. When a service at the bottom goes down, the status 
> > cascades up to upper levels. We are trying to map our HP OpenView 
> > system to Nagios and one of the things we came up against is having a 
> > service hierarchy. Any help is greatly appreaciated.
> > 
> > James Mohr
> > Systembetrieb ____________________________________________________
> > ELAXY Business Solution & Services GmbH & Co. KG.
> > Am Hofbräuhaus 1
> > 96450 Coburg 
> > Germany
> > Fon +49 (0) 95 61.55 43.0
> > Fax +49 (0) 95 61.55 43.302
> > E-Mail: james.mohr at elaxy.com
> > ---------------------------------------
> > "Be more concerned with your character than with your
> > reputation. Your character is what you really are while
> > your reputation is merely what others think you are." -- 
> > John Wooden
> > ---------------------------------------
> > Be sure to visit the Linux Tutorial:
> > http://www.linux-tutorial.info
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 
> > Project Admins to receive an Apple iPod Mini FREE for your judgement 
> > on who ports your project to Linux PPC the best. Sponsored by IBM.
> > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> > _______________________________________________
> > 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
> Mit freundlichen Grüßen aus Nürnberg,
> 
> Gerd Müller



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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