NagVis Automap


The NagVis Automap was introduced in NagVis 1.3. The main topic of this feature is to replace the builtin map in Nagios. The main problem of the Nagios map is that it is not scalable. In big Nagios installations the automap is not usable. This is e.g. caused by missing configuration options like selecting a defined scope of elements to display. NagVis handles the objects and defines a configuration for Graphviz. The map image and the HTML-Code for the links are generated by graphviz and passed on to NagVis.


First call

If you have no experience with the automap yet, take a look at the demo automaps installed with NagVis (demo-automap and demo-automap2). You should be able to open those automaps right after installation of NagVis from the "Open" menu in header navigation. If everything is configured properly the root host and three levels of child hosts should be displayed on the demonstration automap "demo-automap".

Map configuration

In the past, the automaps were configured in special configuration files located in etc/automaps, but this has changed with NagVis 1.7. The automap configuration files are created as regular map configurations (like described in map configuration). To create an automap in NagVis 1.7 you have to set the map source to automap. To do this, you need to add the sources parameter to the global section and set its value to automap.

Main configuration

Some parameters for the automap can be set in the main configuration of NagVis. For further information see Main Configuration.

URL Parameters

The automap can be called with several url parameters. Since NagVis 1.7 these options can be put into the global section of the map configuration to persist those parameters. Here is a list of the automap options:
showThe name of the automap. Since NagVis 1.5 different automap configuration files can be defined. The automap to view needs to be set here.
backend_id backend default backend The backend-id of the backend to fetch the objects from. For details see the [backend_*] section in the Main Configuration
root see root object definition This is the name of the root object. It is not essential to set the host here. There are some more ways to tell the root object. For details see the root object definition chapter on this page.
child_layers childLayers2Maximum layers of child hosts to be displayed.
parent_layers parentLayers0Maximum layers of parent hosts to be displayed.
render_mode renderMode undirected Set the render mode of the map. For details see available render modes
width 1024 width of the automap in pixels
height 786 height of the automap in pixels
ignore_hosts ignoreHosts none comma separated list of hosts (including children) not to display
filter_by_state 0 Set to 1 to enable the "problem automap" mode. When it is set to 1 it will exclude all branches which have only OK/UP hosts. This will result in a "problem automap" which only shows up a tree where each branch has at least one problem.
filter_by_idExclude specified object_ids, is mostly used internal (new in 1.7)
filter_group filterGroupnoneProvide a hostgroup name. Only hosts in this hostgroup will be shown on the map.
searchnoneSearch for a map object on map load. Matching objects will be highlighted.
rankdirLRConfigure direction of directed automaps, can be set to TB (Top/Bottom) and LR (Left/Right) (new in 1.7)
rotationnoneRotate in the given rotation pool when the map is a step in the pool.
header_menu enableHeadernoneEnable/Disable the header menu. To be specified as integer (1/0). Overrides the configuration.
hover_menu enableHovernoneEnable/Disable the hover menus. To be specified as integer (1/0). Overrides the configuration.
context_menu enableContextnoneEnable/Disable the context menus. To be specified as integer (1/0). Overrides the configuration.
margin50Sets the free area on the border of the automap graph. Has to be specified in pixels.
overlaptrueConfigure collision handling of objects (take a look at the graphviz docs for explanations of the values) (new in 1.7)

Root object definition

The approach of the automap is to start at one root object and go down the dependency-tree like defined in Nagios and show all these objects on the map. There are several ways to get the root object: The list above is ordered by priority.

Available render modes

There are several render modes available:
Mode Example image

Automap to Map export

Since NagVis 1.5 it is possible to export the current automap view as a classic NagVis map. Exporting automaps to classic maps you get the advantages of both worlds.

You can start with the automap to get all the object positioned on your maps using the automap render modes. Once you finished the rendering you can export the automap including the generated background image to a regular map using the "Export to map" which can be found in the "Actions" submenu in your header menu.

Using the exported map you can add design elements as you like and customize your layout according to your needs.

A map can be exported multiple times to the same target map but it will overwrite all changes you made to the target map before. You can only overwrite maps you have edit permissions on.

A classic map can not be turned into an automap.

Host URLs

The URLs of the host objects are used for identifying the host objects during automap rendering. Especially the "host=" parameter is important. When this parameter is missing in the host URLs the object positions can not be gathered.

By default this information should not be of interest to you. But when you customize the host URLs in your NagVis installation it is important to know that your custom URL needs to have the "host=" parameter set to the hostname of the object to be able to use the hosts on the automap.