QuickStart Guide - Nagios, Icinga, Centreon, & al.

Overview of this Guide

This guide is wallthrough to get started with RealOpInsight in a few minutes using a Docker image and an integration with Nagios, Icinga, Centreon, and similar systems. For other installation options, i.e. using binaries or a virtual machine image, please refer to our complete Installation Guide.

Before moving forward, note that the below steps assume that:

  • You have a running instance of Nagios, Icinga, Centreon, or any similar system.
  • You have a network-based Livestatus access to your monitoring data. It’s worth noting that Icinga 2 provides a reimplementation of the Livestatus protocol that you can easily enable.

Start a RealOpInsight Docker Instance

The following command will start a RealOpInsight Docker instance:

    $ docker run --network="host" -p 4583:4583 -p 2283:22 -i -t rchakode/realopinsight /bin/bash

This will start a container and bind the following:

  • Access to RealOpInsight Web Interface through port 4583 (http://127.0.0.1:4583/realopinsight/, default credentials: admin/password).
  • SSH access to the containter through 2283 (ssh -p 2283 ubuntu@127.0.0.1, password is ubuntu).

Installation Summary

Once the container is running:

  • The RealOpInsight Web Interface is available at the following URL: http://127.0.0.1:4583/realopinsight/. The default administrator credentials are admin/password. For a prodution setup and must be kept secured the default password must be changed as quick as possible.
  • You can open an SSH access to the Docker instance as follows: ssh -p 2283 ubuntu@127.0.0.1 (password is ubuntu). Inside the container, binaries, logs, and many other configuration files are located at /opt/realopinsight/.

Integrate Nagios, Icinga, Centreon, & al. as Monitoring Data Source

Proceed as follows in order to integrate a Livestatus monitoring data source:

  • Log into RealOpInsight as administrator.
  • Select the menu Monitoring Sources to fill in the monitoring source settings.
  • Set the property Monitoring Source Type to Nagios.
  • Set the property Livestatus Host with the hostname or the IP address of the Livestatus network listener. This would be typically the address of your monitoring server, but you can also imagine a tunnelled remote access from another machine (e.g. RealOpInsight host).
  • Set the property Livestatus Port with the port of the Livestatus network listener (e.g. 6558 with is the default port used set by MK Livestatus and Icinga).
  • Leave all the other properties as is.
  • Click on the button Add as source.
  • When prompted, select Source0 as Source Id.
  • Click on Apply to save the changes.
  • On success you shall see a message confirming that.

For this quickstart a single source is enough, but you can repeat the above steps to add as many monitoring sources as you want to integrate with RealOpInsight.

Autodiscovery & Operations Views With Nagios & al.

As a first and very simple way of starting using RealOpInsight with Nagios, Icinga, Centreon and similar systems, is to automatically discovered monitoring items and organize them within a hierarchical host/group-based operations view, as illustrated hereafter. In this approach, items are discovered basing on a host/group filter that you specify as input for the auto-discovery process.

hostgroup 
  |
  +---host1
  |        |
  |        +--item1
  |        |
  |        +--item2     
  +---host2
  |        |
  |        +--item1 
  |        |
  |        +--item1     

By this way you can ultimately setup operations views that can be watched at the highest level as below. It’s worth noting that this is a very basic way of building operations views using RealOpInsight. Its Web Editor offers rich features to allow you to build specific and highly customizable operations views.

Create Your First Autodicovered Operations View

  • Log into RealOpInsight as administrator.
  • Select the menu Service Editor to launch the editor.
  • Select the button Import Button - Nagios, Icinga, Centreon & al. to load the autodiscovery form.
  • Select a source in the displayed list (only Nagios sources shall be listed).
  • Set a host/group name for filtering the monitoring items to fetch from Livestatus.
    If no filter is set, what is not relevant nor recommended – unless you have a small monitoring installation, all the monitoring items will be fetched.
  • Click on Apply to start the process.
  • On success the operations view associated to the discovered items will be loaded in editor. It shall be named using the value of the host/group filter set. If no filter has been set it shall be named Nagios Services.
  • You can then rename the view as you want by modifying the property Name of the root service from the editor.
  • From the editor you can edit each individual imported item by selecting it from the tree view. You can for example, edit the label associated to the item (Name property) or delete the item (Shift + X) if you don’t want to consider it in your operations view.
  • Click on the button Save Button to save your changes.

Service Operations Console (SOC)

Please read Overview on SOC if needed.

As administrator you can preview and check the Service Operations Console for any single operation view before assigning it for operations.

  • Log into RealOpInsight as administrator.
  • Select the menu Manage Views to see the list of managed views.
  • Select the menu Preview.
  • Select an entry in the list of managed views (e.g. select the entry you created above).
  • Click on Apply to display the view in service operations console.
  • Click on the button to refresh the views (service map, service tree, message panel).

On our example we can see that there are problem on three items. The impact of each event is easily is highlighted using the tree view, the service map and the event console.

Business Operations Dashboard (BOD)

Please read Introduction on BOD if needed.

Unlike SOC, administrators do not have access to BODs but only specific users defined as Operator in RealOpInsight. Each operator has access to a single BOD that acts as its home page on login. A BOD can consist of no, one, or many operation view items organized within a grid with configurable number of columns. As administrator, you need to create BOD operators and explicitly assign operation view items to them.

The rest of this section will describe how to create a operator, to assign operation view items to him, and to login and display a BOD.

Create a Operator User

  • Log into RealOpInsight as administrator.
  • Select the menu New User.
  • Fill in the user information:
    • Password must have at least six (6) characters in two classes (upper/lower cases, digits, special characters, etc.).
    • Ensure to select Operator as User Role.
    • The property Dashboard Tiles Per Row allows to set the number of columns on the BOD grid.
  • Click on Submit to save the changes.

Assign Operations Views

  • Log into RealOpInsight as administrator.
  • Select the menu Manage Views.
  • Select an operator in the user selection list at left.
  • Select one or several items in the list of operation views at the right.
  • Cick on Assign to apply the changes.

Operate a BOD Console

  • Log in as operator
  • On login the operator BOD will be displayed with the items assigned to him.
  • You can select a operation view tile to open the associated SOC.
  • As the SOC is active, you can select Executive View to go back to the BOD.

This is the end of this quickstart of RealOpInsight, please follow the below links to move forward with advanced use.