Centreon Collect is a collection of softwares:

• Centreon Engine
• Centreon Broker
• Centreon Connector

Centreon Collect brings also Centreon tests to test these softwares.

Centreon Engine is a fast and powerful open-source monitoring scheduler.
It is a low-level component of the
Centreon software suite.

Centreon Engine is released under the General Public License version 2
and is endorsed by the Centreon company.

This project was started as a fork of Nagios, the well known open-source
monitoring application. While keeping its configuration file format and
its stability we improved it in several ways:

• Reduced startup time
• Faster standard check execution engine
• New light check execution system (connectors)
• On-the-fly configuration reload
• Less obscure configuration options
• Frequent bugfix releases

Just give it a try!

Centreon Broker is an extensible open-source monitoring event
transmitter (broker). It is a low-level component of the
Centreon software suite.

Centreon Broker is released under the Apache License, Version 2.0
and is endorsed by the Centreon company.

Centreon Broker is the communication backbone of the Centreon software
suite so most events are processed by one or more of its module.
Centreon Broker has multiple modules that perform specific tasks. The
list below describes the most common of them.

• SQL: store real-time monitoring events in a SQL database
• storage: parse and store performance data in a SQL database
• RRD: write RRD graph files from monitoring performance data
• BAM: compute Business Activity status and availability
• Graphite: write monitoring performance data to Graphite
• InfluxDB: write monitoring performance data to InfluxDB

Centreon Broker is extremely fast and is a credible alternative to the
old NDOutils. It is also extremly modular and can fit most network
security requirements. Just give it a try!

Centreon Connector is extremely fast open-source monitoring check
execution daemons designed to work with
Centreon Engine.

It is a low-level component of the
Centreon software suite.

Centreon Connector is released under the Apache Software License version 2
and is endorsed by the Centreon company.

There are currently two open-source connectors :

• Centreon Connector Perl : persistent Perl interpreter that
  executes Perl plugins very fast
• Centreon Connector SSH : maintain SSH connexions opened to reduce
  overhead of plugin execution over SSH

https://docs.centreon.com

Centreon Collect is a low-level component of the Centreon software suite. If this is your first installation you would probably want to install it entirely.

Centreon (the company behind the Centreon software suite) provides binary packages for RedHat / CentOS. They are available either as part of the Centreon Platform or as individual packages on our RPM repository.

Once the repository installed a simple command will be needed to install Centreon Collect.

yum install centreon-broker centreon-clib centreon-connector centreon-engine

Beware that the repository hosts in-development sources and that it might not work at all.

Stable releases are available as gziped tarballs on Centreon's download site.

This paragraph is only a quickstart guide for the compilation of Centreon Collect.

Compilation of these distributions is pretty straightforward.

You'll need to download the project and launch the cmake.sh script to prepare the compilation environment:

git clone https://github.com/centreon/centreon-collect
cd centreon-collect
./cmake.sh

Now launch the compilation using the make command and then install the software by running make install as priviledged user:

cd build
make
make install

If you are on another distribution, then follow the steps below.

Check if you have these packages installed (Note that packages names come from CentOS distributions, so if some packages names don't match on your distribution try to find their equivalent names): git, make, cmake, gcc-c++, python3, libgnutls-devel, liblua-devel, librrd-devel.

For the projet compilation you need to have conan installed. Try to use the package manager given by your OS to install conan. ('apt' for Debian, 'rpm' for Red Hat, 'pacman' for Arch Linux, ...). It is prefered to install gcc before conan.

Example :

apt install conan

If it does not work, conan can be installed with pip3:

pip3 install conan==1.57.0

All the dependencies pulled by conan are located in conanfile.txt. If you want to use a dependency from your package manager instead of conan, you need to remove it from conanfile.txt.

You can now prepare the compilation environment:

git clone https://github.com/centreon/centreon-collect
mkdir -p centreon-collect/build
cd centreon-collect/build
conan install .. --build=missing
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DWITH_TESTING=On -DWITH_MODULE_SIMU=On ..

This will look for required dependencies and print a summary of the compilation parameters if everything went fine.

Now launch the compilation using the make command and then install the software by running make install as priviledged user:

make
make install

Normally if all compiles, you have finished installing Collect. But if you want, you can also check it. Always from the build directory you can execute this command:

test/ut

You're done!

In my case I have the home directory of the centreon project in /data/dev/centreon-collect

First create the ubuntu container and jump into

docker container run --name ubuntu22.04 -ti -v /data/dev/centreon-collect:/root/centreon-collect  ubuntu:22.04 /bin/bash

Now you are in your ubuntu container

cd /root/centreon-collect/
apt update
apt install python3
apt install python3-pip
pip3 install conan
apt install libgnutls28-dev
apt install liblua5.4-dev
apt install librrd-dev
apt install cmake

./cmake.sh 
cd build
make

Then you have all binaries compiled in the ubuntu distribution. You can access it outside the container in the /data/dev/centreon-collect/build directory

The best way to report a bug or to request a feature is to open an issue in GitHub's issue tracker.

Please note that Centreon Collect follows the same workflow as Centreon to process issues.

For a quick resolution of a bug your message should contain:

• The problem description
• Precise steps on how to reproduce the issue (if you're using Centreon web UI tell us where you click)
• The expected behavior
• The Centreon products versions
• The operating system you're using (name and version)
• If possible configuration, log and debug files

Contributions are much welcome! If possible provide them as pull-requests on GitHub. If not, patches will do but describe against which version/commit they apply.

For any question or remark feel free to send a mail to the project maintainers: