AW: Cascading Services/Service hierarchy

[Mohr James]

I'm actually thinking of the reverse. Yes, it is possible that the HTTP service is running but the site is down. It could be any number of situations, such as no access to a database. So from the SLA perspective, the service we are providing (the web site) is down. 

However, if the HTTP service is down, the site is also not accessible (it cannot be!) and again from the SLA perspective, the service we are providing (the web site) is down. If the machine crashes. The machine service is down, thus the HTTP service is down, thus the Web site service is down. With services in HP VantagePoint Operations (VPO), the machine goes down and the service is red, this propogates to the HTTP service and then to the site service. I see that the site service is down and then drill down to see the root cause (the machine crash).  

With Nagios it seems like this kind of propogation is not possible. Although I obvuously need something that monitors to the site services (which we already have), the fact that the machine goes down does not change the status of the site service. If this machine also had FTP, and mail, these services would still be green as well.  On the other hand, the machine going down would turn the VPO services red as well (because they are also not accesible).

I am not saying the the way VPO does it is the "right way". I am just trying to compare how Nagios does it compared to VPO. 

James Mohr

> -----Ursprüngliche Nachricht-----
> Von: Gerd Müller [mailto:gmueller at netways.de] 
> Gesendet: Freitag, 24. September 2004 17:12
> An: Mohr James
> Cc: Nagios-users at lists.sourceforge.net
> Betreff: Re: AW: AW: [Nagios-users] Cascading 
> Services/Service hierarchy
> 
> 
> Sorry I am not sure if I understand your question right. But 
> sounds like you are again mixing up slas with physical 
> services. The availability of your website/shop/... is 
> different from the availability of the webserver. You should 
> define both views. 
> 
> An example: your webserver still can be active but only 
> displays "shop is closed". Wouldn't that be bad ;-) ? So the 
> webserver (http) would be ok but the shop (in this case your 
> sla-service!) would be critical. So both service definitions 
> are esential.
> 
> Gerd  
> 
> BTW: for check_cluster have a look at 
> http://nagios.sourceforge.net/docs/1_0/clusters.html 
> 
> 
> Am Fr, den 24.09.2004 schrieb Mohr James um 16:32:
> > > -----Ursprüngliche Nachricht-----
> > > Von: Gerd Müller [mailto:gmueller at netways.de]
> >  
> > > I see two possible solutins for your situation. First use
> > > "check_cluster" and second - better - abstract the sla view 
> > > from the technical view. that means create own independent 
> > > services for each sla, which will only check if your promised 
> > > service is alive. 
> > > 
> > 
> > Just so I am clear on this. The status is not propogated from a 
> > service to the dependant service. For example, we have a 
> web service that is dependant on the network service. If the 
> network service goes down, the web service is logially not 
> accessible. You can tell Nagios not check the Web services at 
> this point because it makes no sense to if the network is 
> down. However, the status of the Web service is unchanged. I 
> would have to explicitely check the Web service to see if it 
> were down or set the status of the Web service directly, 
> using something like send_nsca.
> > 
> > Is this right?
> > 
> > 
> > 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