Nagios is a software for Network Monitoring which can be configured from data of the IT documentation. By this means, you can avoid that data have to be maintained twice and you can minimize errors. The export function available in i-doit allows the creation of complete or partial configurations. For this purpose, you manually create Nagios configurations in the i-doit interface or you fill it with values automatically.
The exported data are compatible with Nagios Version 3 and Icinga Version 1. Nagios Version 4 is not completely compatible. Other Nagios versions are not supported.
You store the configuration under
Administration → Interfaces / External Data → Monitoring → Export Configuration. The
Local Path defines an absoulte or relative path to the i-doit installation in the file system in which the configuration created by i-doit is to be stored. The
Link to your monitoring tool specifies a basic link to generate links to the monitoring instance from i-doit.
You can create the basic configurations under
Extras → Nagios.
This includes the main configuration, service templates and host templates as well as other basic settings. All values are identical to the Nagios configuration.
Configuration in Objects
All further configurations are carried out within the objects. The easiest case is the configuration of host parameters. For this purpose, the
Nagios (Host)category folder has to be assigned to the desired object type via the
Quick Configuration Wizard
In the category
Host Definition a host definition for Nagios can be set either via a Nagios template or via individual configuration.
The concept of host templates and service templates is identical to the original Nagios configuration.
Service checks defined in the basic configuration are assigned to a host via the
Service Assignment category.
Later on, this results in the configuration of a classic host/ service assignment. Additionally, there is a second way of assigning services to hosts, namely by inheriting through a software object.
A service check is assigned in a software object in the
Nagios (Applications) category, analogous to the assignment to a host.
If this application is installed on a host via the
Software Assignment category, ...
... then the service check is inherited to the host automatically.
Further Nagios configurations within objects can be found in
Persons objects ...
... as well as in
... and in
Export of the Nagios Configuration
The Nagios configurations can be exported manually via
→ Interfaces/ external data → Monitoring → Nagios Export . For this purpose, you select an export configuration and optionally you can also choose a validation of the parameters.
The validation checks basic dependencies, for example, if an IP address has been entered for a host etc. This check is supposed to prevent the generation of corrupt Nagios configurations. This, however, is not a 100% safe protection so you should always run a test with the Nagios binary checking the generated configuration.
The configuration files are stored according to the configured path on the file system and correspond the values that have been configured in the categories.
The export of the files can be automated via the controller of course. For this purpose, the handler
nagios_export is run while stating the export configuration ID using the parameter