Configuring Monitoring Sources

RealOpInsight can manage up to ten monitoring sources simultaneously; a service view can rely on one or many monitoring sources at the same time.

This document guides you through the steps to configure monitoring data sources.

Source Paramaters

According to the target monitoring system, some of parameters may be required, optional, or not applicable at all (NA).

Parameter Description Required
Monitor Web URL Sets the base URL to the web interface of the monitoring server. E.g. http://zabbix-server/zabbix/
  • Yes with Zabbix, Zenoss and Pandora FMS
  • No with Nagios and similar systems
Disable SSL Peer verification

When using secure connection with self-signed certificate, this option disable some SSL controls to avoid handshake failure.

WARNING: USE THIS OPTION AT YOUR OWN RISK. Even if enabling this option doesn’t compromise the cyphering of communication between RealOpInsight and the monitoring server, it disables many SSL security controls such as the verification of the certificate hostname.

  • Yes with Nagios and similar systems
  • Optional, but recommended with others
Auth String

Sets credentials string for authenticating against the remote API endpoint:

  • With Zabbix and Zenoss, this should be set with a couple login:password (note the : separator), representing a valid user account.

    NOTE: Prior to Zabbix 2.0, the user MUST belong to the group API Access.

  • With OpManager, this must be set with an API key (which can be generated/viewed in the settings page)

  • With Pandora FMS, you must set a triplet login, password, API key (optional) as follows: login:password:apikey (note the : separator)

    Additionally, make sure through the Pandora administration page that the RealOpInsight machine’s IP address is enabled to access to the Pandora API.

  • With ngrt4nd, this corresponds to its authentication token. See the corresponding manual for more details

  • Yes: Nagios with ngrt4nd
  • No: Nagios with Livestatus
  • Yes: Zabbix, Zenoss, Pandora FMS Manager OpManager
Server Address Sets the IP address or the hostname of the monitoring server (e.g. server.example.com).
  • Yes for Nagios and similar systems
  • No for others
Port Sets the port on which ngrt4nd or the Livestatus API is listening on on the monitoring server (e.g. 1983 for ngrt4nd).
  • Yes for Nagios and similar systems
  • No for others
Update Interval Set the interval after which the Operations Console will be refreshed with new status information retrieved from the monitoring servers
  • Yes for ALL

Source Configuration

  • Log into RealOpInsight Ultimate as administrator, select the menu Monitoring Settings, and proceed as below.

    ../_images/realopinsght-ultimate-source-settings.png
  • Set source parameters according to the target monitoring system.

  • Make sure to have select the Monitor Type as appropriate, and click on Add as Source;

  • Select the source index from the selection list that will appear. Note that if you set an index of a source that has been already set, the paramaters of that source will be overwritten with no confirmation.

    • Each source has an identifier in the form of "Source"+Index, where Index is a number (E.g. Source0, Source2).
    • It’s not required to set all the sources, but if a source is not set, every service associated to that source will be automatically marked with UNKNOWN status.
    ../_images/realopinsight-ultimate-select-source-index.png
  • Repeat the above steps for all sources you want to manage.