I agree, it sounds like your 2D map will be the same way.
Please read this:
When you defined your hosts.cfg file, you ignored the parent/child relationship entirely. So, you have in your status map, just what you told nagios. You told nagios that NOTHING has a parent, so nagios has to ASSUME that the nagios process itself is the parent.
Of course we know that is NOT true right?
I think most people like nagios to simply monitor hosts. But remember, these hosts connect to a network, and many times, problems are on the network, and not the host. So map out your netork and show that in the 2d status map.
If you read the url I posted above, you will see that what you end up with is this:
Status map now shows the nagios process connected to a host (central nagios server), it connects to it’s eth0 ehternet card, that card connects to a switchA via port 15. Switch A port 1 connects to switchB port 24. HostA connects to SwitchB port 4 via it’s eth0 card. HostB connects to SwitchB via…
You see what I’m getting at? You don’t want 200 hosts, all connected to the nagios process in your status map, it looks rediculous and entirely not logical. These hosts connect to switch ports on a switch. So define them.
You may think thiis is a waste of time. But I"ll tell you, it has helped us alot when a cable is broken, or a port goes bad, etc. It’s happened more than you think. Plus, your boss is going to look at your status map, and say “WOW, we now have a schematic diagram of our complete network layout, GREAT JOB!!”
Edited Mon Oct 17 2005, 12:57AM ]