Monitoring Data Sources

Overview

A monitoring data source, or simply monitoring source, defines a monitoring system where RealOpInsight can retrieve raw monitoring data in order to update the statuses of the business service views it manages.

Supported Monitoring Sources

RealOpInsight currently supports the following monitoring data sources listed in a random order.

Monitoring Source Tested Versions Comments
Kubernetes >= 1.9.x Requires access to Kubernetes API (direct access or through proxy).
Zabbix >= 1.8.0 Requires access to Zabbix API.
Prior to Zabbix 2.0, the user MUST belong to the group API Access
Nagios & Derived systems >= 3.0.0 Requires Livestatus >= 1.2.5i1.
Nagios >= 4.x; GroundWork >= 5.0; Centreon >= 3.x; Icinga >= 1.x; OP5 >= 5.0; Shinken >= 1.0; Check_MK >= 1.1.0
ManageEngine OpManager All versions with REST API
Pandora FMS >= 4.0.2
Zenoss => 4.0

Integration of Monitoring Sources

RealOpInsight is built upon a loosely-coupled architecture where all raw status data are retrieved from the backend monitoring data sources only through API calls. This results to a simplified, yet scalable and interoperable architecture able to handle a wide range of monitoring systems simultaneously.

Configuration of Monitoring Sources

For any monitoring source you want to integrate with RealOpInsight, you need to log in as administrator and set the following settings under the menu Monitoring Sources (see screenshort below):

Source Type
Shall be set to one of supported monitoring sources.
Monitor API Base URL

Applicable for all sources Nagios & derived systems, this setting shall be set with the base URL of the monitoring system API.

E.g. you can use http://zabbix-server/zabbix/ for a Zabbix API running on a machine named zabbix-server; http://k8s-proxy-server:8000/ for a Kubernetes proxy API bound on port 8000 on a machine named k8s-proxy-server.

Disable SSL Peer Verification

Applicable for all sources except Nagios & derived systems, this is optional and allows to disable peer verification during SSL handshake. It may be typically useful when the monitoring source API is enabled through a self-signed certificate.

BE CAUTION: even if this setting doesn’t compromise communication cyphering between RealOpInsight and the target monitoring server, it disables some SSL security checks such as the verification of the certificate hostname.

API Auth String

Sets credentials for authenticating against the remote API. If not explicitly stated for a given monitoring system, this setting should be considered as optional or not needed at all:

  • With Zabbix and Zenoss, it must be set with a couple login:password (note the comma : separator). The tuple login and password shall represent a valid user account in Zabbix. Prior to Zabbix 2.0, the user MUST belong to the group API Access.
  • With ManageEngine OpManager, this must be set with an API key generated under OpManager settings section.
  • With Pandora FMS, you must set it as follows: login:password:apikey (note the comma : separator). The tuple login and password shall represent a valid user account in Pandora FMS; and if set ,apikey shall match a valid API key. Additionally, make sure under the Pandora administration page that the RealOpInsight machine’s address is enabled to access to the Pandora API.
Livestatus Host

Applicable for Nagios & derived systems that require a Livestatus integration, this setting sets the hostname or the IP address of the machine hosting the Livestatus service.

Livestatus Port

Applicable for Nagios & derived systems that require a Livestatus integration, this setting sets the port of the Livestatus service.

Update Interval

This global setting sets the interval after which the Operations Console will be refreshed with new status information retrieved from monitoring data sources.