Icinga

Use BigPanda to view all your noisy Icinga alerts and organize them into high-level incidents.

Supported Versions:

Type:
Agent

Key Features

  • Visualize multiple alerts along an easy-to-use timeline.
  • Assign alerts to team members and track their activities in real-time.

How It Works

A webhook is configured in Icinga, forwarding all alerts to the Icinga integration. The integration then normalizes the alerts and sends them into BigPanda to be processed and correlated with related alerts, creating and maintaining up-to-date incidents in BigPanda.

Installing the Integration

Prerequisites

  • Create an App Key - Enter the name of your integration and click Generate App Key.
    You'll need a separate App Key for each integrated system.

Install the BigPanda Agent

Connect to the host where your Icinga server is installed and install the BigPanda agent package.

$ sudo wget http://repos.bigpanda.io/config/bigpanda.repo -O /etc/yum.repos.d/bigpanda.repo
$ sudo yum install bigpanda-agent

Note: If you run RHEL 5, you will need to install the EPEL repository. Please consult the FAQ for instructions.

$ sudo wget http://repos.bigpanda.io/config/bigpanda.repo -O /etc/yum.repos.d/bigpanda.repo
$ sudo yum install bigpanda-agent

Note: If you run CentOS 5, you will need to install the EPEL repository. Please consult the FAQ for instructions.

$ echo deb http://repos.bigpanda.io/deb `lsb_release -c -s` main | sudo tee /etc/apt/sources.list.d/bigpanda.list
$ curl https://repos.bigpanda.io/config/bigpanda.pub | sudo apt-key add -
$ sudo apt-get update
$ sudo apt-get install bigpanda-agent
$ echo deb http://repos.bigpanda.io/deb `lsb_release -c -s` main | sudo tee /etc/apt/sources.list.d/bigpanda.list
$ curl https://repos.bigpanda.io/config/bigpanda.pub | sudo apt-key add -
$ sudo apt-get update
$ sudo apt-get install bigpanda-agent

Configure Icinga

Open the main Icinga configuration file (usually /usr/local/icinga/etc/icinga.cfg or /etc/icinga/icinga.cfg):

$ sudo vim /usr/local/icinga/etc/icinga.cfg

  1. Set log_rotation_method to d (= daily log rotation).
  2. Make sure log_archive_path is configured (= location of old logs).
  3. Test that Icinga (usually nagios user) has write permissions to the log_archive_path folder.
  4. Reload the Icinga service for the changes to take effect.

sudo service icinga reload

Configure the BigPanda Agent

Generate the agent's configuration file:

$ sudo bigpanda-config --init --token 58836bbfcc02ae9ba60d19f7b52796c4
$ sudo bigpanda-config --add icinga --app-key <your app key>

When prompted, specify the locations of icinga.log, status.dat and objects.cache files.
The script output should look like this:

Log File Path: /var/log/icinga/icinga.log
Status Dat Path: /var/cache/icinga/status.dat
Objects Cache Path: /var/cache/icinga/objects.cache

the actual paths will depend on your installation.

Update Permissions

Give the agent read permissions to the objects.cache, status.dat and log files.
A possible way to do it:

$ sudo usermod -a -G "<GROUP OF OBJECT CACHE FILE>,<GROUP OF LOG FILE>,<GROUP OF STATUS DAT FILE>" bigpanda

Start the BigPanda Agent

# On RHEL 6:
$ sudo initctl start bigpanda

# On RHEL 5 and 7:
$ sudo service bigpanda start

# On CentOS 6:
$ sudo initctl start bigpanda

# On CentOS 5 and 7:
$ sudo service bigpanda start

$ sudo service bigpanda start

$ sudo service bigpanda start

👍

Success!

You should be able to see all your active Icinga alerts in the Incidents tab.

For FAQs about integrating Icinga, see the Icinga Integration page, located in the BigPanda Integrations tab.

Updated 9 months ago


Icinga


Use BigPanda to view all your noisy Icinga alerts and organize them into high-level incidents.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.