Nagios Statusmap – trash it!

The statusmap of Nagios is delivered with the default web interface since more than 10 years now. There was no major change or innovation in the Nagios statusmap in this time. Even within the Icinga fork there was no real change to make the statusmap more usable.

My major args against the Nagios statusmap:

• Quickly overloaded by about 30 objects on the map
• No custom height/width configurable
• The root object can not be selected (The Nagios process is always the root)
• The scope of objects can not be limited by number of layers
• Not possible to filter out non-problem states
• Object actions like hover, left- and rightclick are not customizable
• No drill down capability

If you like to visualize less than ~30 objects in a static way then the statusmap is good for you. When you need to visualize more than this amount of object or like to have a flexible map you should not waste your time in making the statusmap compile or search for valid gdlibs on your system.

It was not my intend to advertise at this place I mainly wanted to point out my opinion that the statusmap is useless but I think it is important to write that all those features are addressed by the automap feature of NagVis.