How RealOpInsight Works

RealOpInsight allows to leverage the capabilities of existing monitoring systems in a unified and integrated framework enabling effective operations management. Compatible with Nagios, Zenoss, Zabbix, Pandora FMS, Icinga, Shinken, Centreon, GroundWork, op5, to name a few, it can also be easily extended to support most of existing monitoring systems. In addition to its wide range of interoperability, RealOpInsight has been designed to make its integration easy, even in distributed and large monitoring environments.

This document introduces the set of supported monitoring systems (also called monitoring sources in RealOpInsight terminology), and describes how RealOpInsight interacts with each of them.

The Supported Monitoring Sources

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

RealOpInsight currently supports more than a dozen of monitors listed in the following section. Here is an alphabetical list of monitors currently supported by RealOpInsight.

Monitor Versions Tested Comments
Centreon >= 3.x Requires MK Livetstaus
Check_MK >= 1.1.0 Requires MK Livetstaus
ManageEngine OpManager Any version having the REST API SDK  
Pandora FMS >= 4.0.2  
Icinga >= 1.x Requires MK Livetstaus
GroundWork >= 5.0 Requires MKLivetstaus
Nagios >= 3.0.0 Requires Livestatus (>= 1.2.5i1 for Nagios 4)
op5 >= 5.0 Requires Livestatus
Shinken >= 1.0  
Zabbix >= 1.8.0  
Zenoss >= 4.0.0  

System Architecture

RealOpInsight is built upon a loosely-coupled architecture to simplify its integration with the underlying monitoring systems. In this architecture, any status data is retrieved from the backed monitoring systems only through RPC APIs. This results to a scalable and powerful architecture able to handle large number of distributed, homogeneous, and heterogeneous monitoring systems simultaneously. This makes RealOpInsight especially useful for monitoring cloud environments.

The mechanism used to retrieve the status data depends on the underlying monitoring systems:

  • For Pandora FMS, RealOpInsight relies on its HTTP-based API.
  • For Zabbix, RealOpInsight relies on its native Zabbix API.
  • For Zenoss, it relies on its JSON-RPC API.
  • For Nagios and derived systems, RealOpInsight relies on MK Livestatus. Since Nagios does not provide native API, MK Livestatus appeared as a proved and effective approach to retrieve status data in real time. Alternatively, but only recommended for testing purpose, you can also use ngrt4nd, our specific daemon that relies on status.dat to serve Nagios status data for remote clients.
../_images/realopinsight-ultimate-architecture.png

Architecture of RealOpInsight Ultimate

[1]http://mathias-kettner.de/checkmk_livestatus.html
[2]http://www.shinken-monitoring.org/wiki/livestatus_shinken