Skip to main content
Version: ⭐ 23.10

Technical information

Tables of network flows​

Tables of network flows to integrate monitoring platform to IT​

Central server​

FromToProtocolPortApplication
Central serverNTP serverNTPUDP 123Synchronization of the system clock
Central serverDNS serverDNSUDP 53Domain name resolution
Central serverSMTP serverSMTPTCP 25Notification via email
Central serverLDAP(s) serverLDAP(s)TCP 389 (636)Authentication to access the Centreon web interface
Central serverDBMS serverMySQLTCP 3306Access to Centreon databases (if moved to a dedicated server)
Central serverHTTP ProxyHTTP(s)TCP 80, 8080 (443)If your platform needs to connect to a web proxy to access the Centreon IT Edition
Central serverRepositoryHTTP (FTP)TCP 80 (FTP 20)Repository for system and application packages

Poller​

FromToProtocolPortApplication
PollerNTP serverNTPUDP 123Synchronization of the system clock
PollerDNS serverDNSUDP 53Domain name resolution
PollerSMTP serverSMTPTCP 25Notification via email
PollerRepositoryHTTP (FTP)TCP 80 (FTP 20,21)Repository for system and application packages

Remote Server​

FromToProtocolPortApplication
Remote ServerNTP serverNTPUDP 123Synchronization of the system clock
Remote ServerDNS serverDNSUDP 53Domain name resolution
Remote ServerSMTP serverSMTPTCP 25Notification via email
Remote ServerLDAP(s) serverLDAP(s)TCP 389 (636)Authentication to access the Centreon web interface
Remote ServerDBMS serverMySQLTCP 3306Access to Centreon databases (if moved to a dedicated server)
Remote ServerRepositoryHTTP (FTP)TCP 80 (FTP 20)Repository for system and application packages

Other flows can be necessary for Centreon web authentication (RADIUS, etc.) or notification system defined.

Tables of platform flows​

Poller​

FromToProtocolPortApplication
Central serverPollerZMQTCP 5556Export of Centreon configuration (depending on communication type)
Central serverPollerSSH (legacy)TCP 22Export of Centreon configuration (depending on communication type)
PollerCentral serverBBDOTCP 5669Transfer of collected data
PollerCentral serverHTTP(S)TCP 80 (443)Poller registration

Remote Server​

FromToProtocolPortApplication
Central serverRemote ServerZMQTCP 5556Export of Centreon configuration
Remote ServerCentral serverBBDOTCP 5669Transfer of collected data
Remote ServerCentral serverHTTP(S)TCP 80 (443)Remote Server registration
Remote ServerPollerZMQTCP 5556Export of Centreon configuration (depending on communication type)
Remote ServerPollerSSH (legacy)TCP 22Export of Centreon configuration (depending on communication type)
PollerRemote ServerBBDOTCP 5669Transfer of collected data
PollerRemote ServerHTTP(S)TCP 80 (443)Poller registration

If Remote Server is not used as proxy for a Poller, Poller network flows apply.

Monitoring​

FromToProtocolPortApplication
PollerNetwork equipment, servers, etc.SNMPUDP 161Monitoring
Network equipmentPollerTrap SNMPUDP 162Monitoring
PollerServersNRPETCP 5666Monitoring
PollerServersNSClient++TCP 12489Monitoring

If the Centreon server is a poller too, remember to open monitoring flows.

Other flows can be necessary to monitor databases, access to API, or application ports.

Users and groups​

Description of software and linked users:

SoftwareServiceUserComment
Apachehttpdapacheautomatic start
PHP-FPMphp-fpmapacheautomatic start
MariaDBmariadbmysqlautomatic start
Centreoncentreontrapdcentreonautomatic start
Centreon Brokercbwdcentreon-brokerautomatic start
Centreon Brokercbdcentreon-brokerautomatic start
Centreon Enginecentenginecentreon-engineautomatic start
Centreon Gorgonegorgonedcentreon-gorgoneautomatic start

Description of optional software and linked users:

SoftwareServiceUserComment
Centreon VMwarecentreon_vmwarecentreonnot installed by default
RRDtoolrrdcachedrrdcachednot enabled and not defined in Centreon by default

Description of groups and linked users for Centreon Open Source and IT Edition:

GroupUsers
apachenagios,centreon,centreon-gorgone
centreoncentreon-engine,centreon-broker,apache,centreon-gorgone
centreon-brokercentreon,nagios,centreon-engine,apache,centreon-gorgone
centreon-enginecentreon-broker,apache,nagios,centreon,centreon-gorgone
centreon-gorgonecentreon,apache,centreon-gorgone,centreon-engine,centreon-broker
rrdcachedcentreon-broker,apache

Description of groups and linked users for Centreon Business Edition:

GroupUsers
apachenagios,centreonBI,centreon,centreon-gorgone
centreoncentreon-engine,centreon-broker,apache,rrdcached,centreonBI,centreon-gorgone
centreon-brokercentreon,nagios,centreon-engine,apache,rrdcached,centreon-gorgone
centreon-enginecentreon-broker,apache,nagios,centreon,centreon-gorgone
centreon-gorgonecentreon,apache,centreon-gorgone,centreon-engine,centreon-broker
centreonBIapache
centreon-map
mysqlcentreonBI

Description of users, umask and home directory for Centreon Open Source and IT Edition:

UserumaskhomeShell
root0022/root/bin/bash
apache0022/var/www/sbin/nologin
centreon0002/var/spool/centreon/bin/bash
centreon-broker0002/var/lib/centreon-broker/bin/bash
centreon-engine0002/var/lib/centreon-engine/bin/bash
centreon-gorgone0002/var/lib/centreon-gorgone/bin/bash
mysql0002/var/lib/mysql/sbin/nologin
rrdcached0002/var/rrdtool/rrdcached/bin/bash

Description of users, umask and home directory for Centreon Business Edition:

UserumaskhomeShell
root0022/root/bin/bash
apache0022/var/www/sbin/nologin
centreon0002/var/spool/centreon/bin/bash
centreonBI0002/home/centreonBI/bin/bash
centreon-agent0002/var/lib/centreon-agent/bin/bash
centreon-broker0002/var/lib/centreon-broker/bin/bash
centreon-engine0002/var/lib/centreon-engine/bin/bash
centreon-gorgone0002/var/lib/centreon-gorgone/bin/bash
centreon-map0002/home/centreon-map/bin/bash
mysql0002/var/lib/mysql/sbin/nologin
rrdcached0002/var/rrdtool/rrdcached/bin/bash

Software dependencies​

For your information, the following table describes the software dependencies. Everything comes prepackaged with Centreon; you do not need to install anything manually.

SoftwareVersion
Apache2.4
GnuTLS>= 2.0
Net-SNMP5.7
openssl>= 1.0.1k
PHP8.1
RRDtools1.4.7
zlib1.2.3

Architectures​

Standalone central server​

If you are not monitoring many hosts, you may only need one central server.

Components​

The following components are used in a central server:

  • Apache web server for the Centreon web interface
  • MariaDB databases to store Centreon configuration parameters as well as monitoring and performance data
  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL using cbmod by the monitoring engine
  • Centreon Broker SQL stores information in MariaDB databases and forwards them to Centreon Broker RRD
  • Centreon Broker RRD generates and updates RRD files with data in order to display performance graphs

Architecture​

The diagram below summarizes how a central server works:

image

Distributed architecture​

Description (Distributed)​

The distributed architecture has the following elements:

  • A central Centreon server to display information
  • One or more remote servers and/or pollers to collect data

The central Centreon server includes the following items:

  • Centreon web interface
  • Databases (MariaDB + RRD)
  • Monitoring Engine
  • Broker

The Poller includes the following items:

  • Monitoring Engine
  • Broker module to forward collected data to a central broker

This architecture is used for:

  • Enabling load balancing across multiple remote monitoring servers
  • Network stream isolation: if your monitoring architecture has to monitor a DMZ area, it is easier (and safe) to place a remote server in the DMZ network

Components​

Central Centreon server​

Many components are used to build a central Centreon server:

  • Apache web server for Centreon web interface
  • MariaDB databases to store Centreon configuration parameters as well as monitoring and performance data
  • The Centreon Gorgone process is used to send the monitoring configuration to the remote server and to manage it
  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL using cbmod by the monitoring engine
  • Centreon Broker SQL stores information in MariaDB databases and forwards them to Centreon Broker RRD
  • Centreon Broker RRD generates and updates RRD files with data in order to display performance graphs
Poller​

Many components are used to build a poller:

  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL using cbmod by the monitoring engine

Architecture​

The diagram below summarizes the architecture:

image

Remote DBMS​

The distributed architecture with remote DBMS includes three types of entities:

  • A central Centreon server to display information
  • A DBMS server to store collected data
  • One or more remote servers to collect data

The central Centreon server includes the following items:

  • Centreon web interface
  • Monitoring Engine
  • Broker
  • RRD files

The DBMS server stores information in MariaDB databases.

The poller includes the following items:

  • Monitoring Engine
  • Broker module to forward collected data to a central broker

This architecture is used for:

  • Enabling load balancing across multiple remote monitoring servers
  • Network stream isolation: if your monitoring architecture has to monitor a DMZ area, it is easier (and safe) to place a remote server in the DMZ network
  • Providing a remote DBMS

Components​

DBMS server​

The DBMS server is used only to store Centreon configuration parameters as well as monitoring and performance data in MariaDB databases

Central Centreon server​

Many components are used to build a central Centreon server:

  • Apache web server for Centreon web interface
  • The central Centreon server obtains configuration and collected data from the DBMS server
  • The Centreon Gorgone process is used to send the monitoring configuration to the remote server and to manage it
  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL using cbmod by the monitoring engine
  • Centreon Broker SQL stores information in MariaDB databases and forwards them to Centreon Broker RRD
  • Centreon Broker RRD generates and updates RRD files with data in order to display performance graphs
Poller​

Many components are used to build a poller:

  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL by the monitoring engine, using cbmod

Architecture​

The diagram below summarizes the architecture:

image

Remote Server​

The distributed architecture with Remote server includes three types of entities:

  • A Centreon Central server to configure monitoring and to display and operate on collected data
  • One or more Centreon Remote servers to display and operate on a subset of collected data
  • One or more pollers to collect data

The central Centreon server includes the following items:

  • Centreon web interface (configure, display and operate)
  • Monitoring Engine
  • Broker
  • Databases (MariaDB + RRD)

The Remote servers include the following items:

  • Centreon web interface (display & operate a subset of data)
  • Monitoring Engine
  • Databases (MariaDB + RRD)
  • Broker module to forward collected data to a central broker

This architecture is used for:

  • Enabling load balancing across multiple remote monitoring servers
  • Network stream isolation: if your monitoring architecture has to monitor a DMZ area, it is easier (and safe) to place a remote server in the DMZ network
  • Having a dedicated web interface to display and operate on a subset of data.

Components​

Central Centreon server​

Many components are used to build a Centreon server:

  • Apache web server for Centreon web interface
  • MariaDB databases to store Centreon configuration parameters as well as monitoring and performance data
  • The Centreon Gorgone process is used to send the monitoring configuration to the remote server and to manage it
  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL using cbmod by the monitoring engine
  • Centreon Broker SQL stores information in MariaDB databases and forwards them to Centreon Broker RRD
  • Centreon Broker RRD generates and updates RRD files with data in order to display performance graphs
Remote monitoring server​

Many components are used to build a remote server:

  • Apache web server for Centreon web interface
  • MariaDB databases to store monitoring and performance data
  • The Centreon Gorgone process is used to operate on collected data
  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL using cbmod by the monitoring engine
  • Centreon Broker SQL stores information in MariaDB databases and forwards them to Centreon Broker RRD locally. All information is forwarded to the Centreon central server.
  • Centreon Broker RRD generates and updates RRD files with data in order to display performance graphs
Poller​

Many components are used to build a poller:

  • A monitoring engine to collect data
  • Collected data are sent to Centreon Broker SQL by the monitoring engine, using cbmod

Architecture​

The diagram below summarizes the architecture:

image