Configuring NagVis

Version 1 by Bren Eckles
on Mar 11, 2016 14:37.

compared with
Current by Bren Eckles
on Nov 28, 2017 16:01.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
h5. 2.2. Map Configuration

* The NagVis configuration file format is very similar to the format used by Nagios. Configuration statements start with the keyword " *define* " followed by a type field and a left curly bracket. Every following line defines variable-value pairs, separated by a " *=* " until a right curly bracket is found. Hashes " *\#* " are used to mark comments, note that a comment line _MUST_ start with a hash and not with other chars like white spaces.
* *Object Type Descriptions*
** *Global*
** Performance view object defined as popup button with hover menu.
** *Configuration* \-See the options in the [NagVis Configuration] to configure a Performance view object. The requirement is that you must have at least one performance view defined in _GroundWork Monitor_.

h4. 5.0 NagVis Extending
cp -r nagvis /usr/local/groundwork/nagvis/share/userfiles/templates{noformat}
* *Configure* \- Now you should be able to use the new template in _NagVis_. You only have to configure the maps or objects to use the template.
** *Header-Templates* \- You can set the header template in the main configuration of NagVis or in the global section of the map configuration. For details see [NagVis Configuration].
** *Hover-Templates* \- You can set the hover template in the main configuration for all your maps, in the global section of a map for all the objects on this map or in each object for having a custom hover menu for special objects. For details see [NagVis Configuration].
* *Custom Context Menu Actions*
** The context menus basically are right-click menus on the status icons. You can customize these menus by simply editing some template files. The template files are simple html files including some macros which are replaced during render time in _NagVis_.