Documentation forAppOptics

Nagios

Overview

This integration collects metrics from Nagios.

This integration is currently available for Linux platforms.

This integration was updated to V2 plugin framework. If you are still using depreciated way of configuring it, please refer to old documentation.

Setup

The nagios monitoring is accomplished by bridge plugin which is included with the SolarWinds Snap Agent by default. Please follow the directions below to enable it for a agent instance. The bridge plugin utilize Telegraf Exec plugin.

Configuration

The agent provides an example task file to help you get started quickly, but requires you to provide the correct settings for your Nagios installation. In this example we are running a check_load command. To enable the task:

  1. Make a copy of the Nagios example task file /opt/SolarWinds/Snap/etc/tasks-autoload.d/task-bridge-nagios_exec.yaml.example, renaming it to /opt/SolarWinds/Snap/etc/tasks-autoload.d/task-bridge-nagios_exec.yaml:

    Copy
    $ sudo cp /opt/SolarWinds/Snap/etc/tasks-autoload.d/task-bridge-nagios_exec.yaml.example /opt/SolarWinds/Snap/etc/tasks-autoload.d/task-bridge-nagios_exec.yaml
  2. Edit the task file with settings specific to your case, for example:

    If you wish to also collect logs for this service, uncomment the last section in the example task file. For more information on collecting logs, see the logs collector docs.

    Copy
    ---
    version: 2

    schedule:
      type: cron
      interval: "0 * * * * *"
      
    plugins:
      - plugin_name: bridge
      
        config:
          exec:
            ## Commands array
            commands:
              - "/usr/lib/nagios/plugins/check_load -w 5,6,7 -c 7,8,9"
              
            ## Timeout for each command to complete.
            timeout: "5s"
            ## measurement name suffix (for separating different commands)
            # name_suffix: "_mycollector"
            
            ## Metric name prefix
            bridge_prefix: "nagios"
            data_format: "nagios"
            
        tags:
          collector_plugin: "nagios"
          
        publish:
          - plugin_name: publisher-appoptics
          
    ## If you want to gather logs for this integration, uncomment the following section.
    #  - plugin_name: logs
    #    config:
    #      sources:
    #        log_files:
    #          file_paths:
    #            - path: /usr/local/nagios/var/nagios.log
    #            - path: /var/log/nagios3/nagios.log
    #    publish:
    #      - plugin_name: publisher-appoptics
  3. Restart the agent:

    Copy
    $ sudo service swisnapd restart
  4. Enable the Nagios integration in AppOptics

    On the Integrations Page you will see Nagios integration available if the previous steps were successful. It may take a couple minutes before the Nagios integration is identified. Select the Nagios integration to open the configuration menu in the UI, and enable it. If you do not see it, see Troubleshooting Linux..

Testing Integration

To check if and what metrics can be collected with given configuration, run bridge plugin in debug mode:

Copy
$ /opt/SolarWinds/Snap/bin/snap-plugin-collector-bridge --debug-mode --plugin-config "{\"exec\": {\"commands\": [\"/usr/lib/nagios/plugins/check_load -w 5,6,7 -c 7,8,9\"], \"bridge_prefix\": \"nagios\", \"data_format\": \"nagios\"}}"

Metrics and Tags

The collected metrics will be prefixed with nagios.* in AppOptics (or the configured value for bridge_prefix on the task configuration).

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.