Nagios
This page describes StackState version 4.1.
The StackState 4.1 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.1 version range to upgrade to a more recent release.
What is the Nagios StackPack?
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
Prerequisites
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.
Configuration
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.
Enable Nagios integration
To enable the Nagios check and begin collecting data from your Nagios instance:
Edit the Agent integration configuration file
/etc/stackstate-agent/conf.d/nagios.d/conf.yaml
:Include details of your Nagios instance:
nagios_conf - path to the
nagios.cfg
file
By default the Nagios check will not collect any metrics. To enable data collection, set one or both of the following to True:
collect_host_performance_data
collect_service_performance_data.
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.
Permissions for Nagios files
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.
Last updated