Skip to main content
Version: ⭐ 22.04

Architectures

Centreon allows several choices in the composition of the architecture of your monitoring tool. In a relatively simple architecture with a server hosting all services, the architecture can also be organized around a strategic division that distributes the load over multiple collection servers with the establishment of collection points across multiple continents.

Available architectures​

You will find here all architectures supported:

Description (Simple architecture)​

The simple architecture is to have all oversight entities within the same server, ie:

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

This architecture is the simplest a user may encounter.

Components​

Many components are used to build this architecture:

  • Apache web server for 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 monitoring engine
  • Centreon Broker SQL allows to store information into MariaDB databases and forward 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 the architecture:

image

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 deported 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 deported 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, do not forget to open monitoring flows.

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