From: Carl D. <li...@ts...> - 2006-04-05 21:02:28
|
Thank you, this now works as I had hoped. Carl n Sat, 2006-04-01 at 19:45 +0200, Hugo van der Kooij wrote: > On Sat, 1 Apr 2006, Carl Davis wrote: , > > I think I have service dependencies backwards in my head. If I were > > utilizing a flow chart and b required service on a to be up, I would put > > a as the dependent_service_description and b as the host_name? I have a > > long line of wireless links and if the first one fails I do not want to > > be notified that the others will fail as well. > > > > Is the status map built from service dependencies, because it appears > > correctly, however I get service notifications for everything when we > > have a link problem. > > The status maps does not care about dependencies. It only uses the parent > field. > > Assume router arwen and host bilbo. You can only reach bilbo through > arwen. (Or at least your Nagios checks.) > > Then you would define: > > define hostdependency { > dependent_host_name bilbo > hostname arwen > ..... > > I admit it takes some reading and it is propably even more confusing for > those whose native language is not English. > > I would have expected: > > define hostdependency { > hostname bilbo > depend_on_hostname arwen > .... > > I do recommend to rewrite this to be less ambigious in v3. > > Hugo. > |