Nagios

StackState curated integration

This page describes StackState v4.4.x.

The StackState 4.4 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.4 version range to upgrade to a more recent release.

Go to the documentation for the latest StackState 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:

1. 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.

     # Section used for global Nagios check config
     init_config:
     # check_freq: 15 # default is 15
     
     instances:
     - nagios_conf: <nagios_conf_path>          # /etc/nagios/nagios.cfg
       # collect_events: False                  # default is True
       # passive_checks_events: True            # default is False
       collect_host_performance_data: True      # default is False
       collect_service_performance_data: True   # default is False

2. Restart the StackState Agent(s) to publish the configuration changes.

3. 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.

Release notes

Nagios StackPack v2.6.3 (2021-07-19)

• Improvement: Remove API-Integration references from the documentation.

Nagios StackPack v2.6.2 (2021-04-09)

• Bugfix: Fixed release notes issue.

Nagios StackPack v2.6.1 (2021-04-02)

• Improvement: Common bumped from 2.5.0 to 2.5.1.

• Bugfix: Fixed upgrading Nagios StackPack when you upgrade StackState from 4.2.x to 4.3.x

Nagios StackPack v2.6.0 (2021-04-02)

• Improvement: Enable auto grouping on generated views.

• Improvement: Update documentation.

• Improvement: Common bumped from 2.2.3 to 2.5.0

• Improvement: StackState min version bumped to 4.3.0

Nagios StackPack v2.5.0 (2021-02-05)

• Improvement: Separated event streams and health checks for Host Alert and Service Alert events

• Feature: Added event stream for passive service state events

• Feature: Added event stream for service notification events

• Feature: Added event stream and health check for service flapping events

• Feature: Added event stream and health check for host flapping alerts

Nagios StackPack v2.4.1 (2020-11-02)

• Bugfix: Fix for Component State evaluation in Service check.

Nagios StackPack v2.4.0 (2020-09-25)

• Feature: Added support for ITRS OP5 Monitor.

Nagios StackPack v2.3.1 (2020-08-18)

• Feature: Introduced the Release notes pop up for customer.

Nagios StackPack v2.3.0 (2020-08-04)

• Improvement: Deprecated stackpack specific layers and introduced a new common layer structure.

• Improvement: Replace resolveOrCreate with getOrCreate.