Organizing Hosts Services and Contacts

[bobnamac]

Parent/child is indeed the first thing I will setup and put on a dashboard when Nagios arrives. I'm curious if anyone has found this to be helpful when T/S'ing a path through all your infrastructure (switches, routers, F5's)? Our webshop is having entire F5 pools going red (offline per the health monitor). I think it's the VM's they are on but would like to show with a graph of the data path from outside through the network to the F5 that there is never a problem at an intermediate step.

What I'm not sure of is if the map lends itself well the the entire network path, any experience anyone with this?

[abrist]

What I'm not sure of is if the map lends itself well the the entire network path, any experience anyone with this?

Yeas, and the map does a fine job. What you need to remember is that parent-child relationships are configured from the nagiso server's perspective. I also find that using dummy hosts to represent transparent networking devices can be used to identify when those transparent devices are possibly down (as all children will be red).

[bobnamac]

Thanks. Would you mind defining "from the point of view of Nagios"? Is it the only entity that can be the center of the network?

[abrist]

Is it the only entity that can be the center of the network?

Essentially, yes. The nagios server cannot be a child of another object. All objects are children of nagios.