From: Brian L. <kn...@gm...> - 2006-12-22 01:31:16
|
I'm not sure on the ease, but it seems like it should be doable now for any service/application for which you can run a Nagios check against. The parent being the system (ping?), the next some base OS subsystem, next the app that depends on it (log file checks or some other homegrown verification), etc.. Right? Or am I over-simplifying the issue? I do this, as do a lot of us I'm sure, in a very simple form now. Nagios checks that my cacti server is up by checking the host, apache then the cacti log - and they appear that way on the map as well. On 12/21/06, Chris Moody <cm...@qu...> wrote: > This would be AWESOME(!!!) if it were easily implementable. > > Cheers, > -Chris > > Todd Mcneill wrote: > > > It might also be interesting to see if there is a way to visually > > represent these service dependencies on the Status Map. I have people > > that are interested in viewing the status of the entire multi-tier > > application stack by application, but this is difficult the way it is > > represented now. I can create Host Groups for each application, and > > that should translate to a drawing layer on the Status Map, but from > > what I understand, it won't necessarily show me the status of the > > application if, for example, an instance of an httpd daemon that the > > application depends on goes down. |