Monitoring the reporting server

To ensure the maximum uptime of Centreon Monitoring Business Intelligence (MBI) and its services, we highly recommend that you monitor the reporting server. You can implement this monitoring system simply by using the Plugin Pack system or by installing the required indicators manually.

Method 1: To implement monitoring through Centreon Plugin Packs

Install centreon-pack-applications-monitoring-centreon-mbi.

The Plugin Pack centreon-pack-applications-monitoring-centreon-mbi enables monitoring of the critical processes and state of the reporting server. To install the pack, launch the following command on your monitoring platform (central server):

yum install centreon-pack-applications-monitoring-centreon-mbi

Once the Plugin Pack is installed, follow the procedure in the documentation. We advise you to link your reporting server to the App-DB-MySQL template. You will first have to create a MySQL user for this template.

Method 2: To add monitoring manually

If you have not purchased Centreon Plugins Packs, instead you can manually install all the indicators for monitoring your reporting server.

Monitoring the processes

The following processes must be running on the reporting server:

Name Description
mysqld Database server hosting Centreon MBI datawarehouse
cbis Job scheduler for the report generation

Here is an example of a check command to monitor the mysqld process and memory consumption:

$USER1$/centreon_plugins.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=$IP_SERVEUR_REPORTING$ --snmp-version=$SNMP_VERSION$ --snmp-community=$SNMP_COMMUNITY$ --process-status --process-name='^mysqld$' --regexp-name --regexp-path --regexp-args --critical='1:1' --memory

Monitoring Datawarehouse integrity

A plugin is provided with Centreon MBI for checking:

  • That the content of the database is up to date.
  • The number of jobs in a “failed” state.

This plugin should be run once a day, after executing the ETL processes (~10:00 am). You can run this plugin remotely by using check_by_ssh. The options are:

  • Data integrity check:

    /usr/share/centreon-bi/etl/centreonbiMonitoring.pl --db-content
The plugin returns CRITICAL and displays the name and the last entry of the tables which are not up to date. This check take few seconds. Set the timeout of the check to 30 seconds or adjust it, if necessary.
  • Number of failed jobs:

    /usr/share/centreon-bi/etl/centreonbiMonitoring.pl --jobs

The plugin returns the number of failed jobs. If > 0, their state is CRITICAL.

Monitoring server capacity

The following checks will help to anticipate any change in the reporting server capacity:

  • Load average
  • CPU consumption (by core and the average)
  • RAM (independently of the SWAP)
  • SWAP (independently of the RAM)
  • Storage space
  • I/O disk.

ETL log file

A search for the keywords “FATAL” or “ERROR” should be made in the following file:

File Infomation logged
/var/log/centreon-bi/centreonBIETL.log
  • Data synchronization between the monitoring and the reporting server
  • Preparation of dimensions for statistical data analysis
  • Calculation of host and services events and availability statistics
  • Calculation of performances data

Monitoring the license

On the monitoring server you can check the expiration date of the following license: /usr/share/centreon/www/modules/centreon-bi-server/license/merethis_lic.zl. Compare the “Expires” field with the system date.