The Nagios StackPack allows StackState to connect to Nagios. We support the Nagios version 5.x onwards.
Using this StackPack, you can:
map Nagios alerts onto your topology
The following prerequisites need to be met:
StackState Agent V2 must be installed on a single machine which can connect to Nagios and StackState.
A Nagios instance must be running.
The Nagios StackPack requires the following parameters to collect the topology information:
Nagios HostName -- the Nagios HostName from which topology need to be collected.
NOTE - Make sure once Nagios is installed properly, you configure your
hostname and rename from
localhost to proper fully qualified domain name.
To enable the Nagios check and begin collecting data from your Nagios instance:
Edit the Agent integration configuration file
Include details of your Nagios instance:
nagios_conf - path to the
By default the Nagios check will not collect any metrics. To enable data collection, set one or both of the following to True:
# Section used for global Nagios check configinit_config:# check_freq: 15 # default is 15instances:- nagios_conf: <nagios_conf_path> # /etc/nagios/nagios.cfg# collect_events: False # default is True# passive_checks_events: True # default is Falsecollect_host_performance_data: True # default is Falsecollect_service_performance_data: True # default is False
Restart the StackState Agent(s) to publish the configuration changes.
Once the Agent is restarted, wait for the Agent to collect data and send it to StackState.
Nagios StackState Agent check tails Nagios config and log files, so it should have permission to read those files. If you run StackState Agent with some other user than
root, the StackState Agent user must be added to the same group that is attached to the config and log files. Note that manually setting read permission is not an option as the files can sometimes be recreated by Nagios.