Centreon MBI architecture¶

This chapter is about Centreon MBI architecture. The objective is to give you an overview of its architecture and its integration with the monitoring software Centreon.

It’s addressed to administrators who will install or configure Centreon MBI.

The software architecture diagram.
The RPMs architecture diagram.

Only one architecture possible : a dedicated reporting server¶

This architecture and the pre-requisites explained later on that page are necessary for :

Test environnements.
Pre-production environments.
Production environments.

The schema below shows Centreon MBI ‘s main components :

The monitoring database might be on a dedicated server

ETL : Extract, transform and load data into the reporting database
CBIS : Scheduler that manage jobs execution and publication
Reporting database : MariaDB database that contains reporting data and some raw data coming from the monitoring database

Table of network flows¶

In the table below you can find the different flows between the dedicated BI server, Centreon server and databases, by default.

Application	Source	Destination	Port	Protocol
ETL/CBIS	Reporting server	Centreon Database	3306	TCP
SSH	Reporting server	Centreon	22	TCP
CBIS	Centreon	Reporting server	1234	TCP
CBIS	Reporting server	Centreon	80	HTTP*
Widgets	Centreon	Reporting server	3306	TCP

**Only needed for Host-Graph-v2 and Hostgroup-Graph-v2 reports*

Centreon MBI’s RPMs¶

Centreon MBI installation is based on two main modules :

Centreon-bi-server: Centreon MBI interface integrated into Centreon frontend.
Centreon-bi-reporting-server: All the components needed to run the reporting server: report scheduler, ETL, standards reports.

You have to install the database (MariaDB) manually. We highly recommand you to install the database on the same server for performance & isolation considerations.

The schema below show the main RPM packages that compose Centreon MBI. Dependancies linked to these packages are installed but not displayed on this schema.