Meta-services, why should you use them

Do you know the meta-services in Centreon?

Often misunderstood, the meta-services are rarely used. But they are a real added-value for those who know how to manage them. The information that meta-services produce can bring a good knowledge of your IT. This information concern real-time monitoring and performance graphs. This article, based on our expertise and experience, aims to present the meta-services and explain how to use and configure them.

Continue reading

Incoming search terms:

  • centreon meta service
  • meta services
  • check meta services
  • configure meta service centreon

A Happy New Year with Centreon and 3 New Versions

At Merethis, we all wanted to wish you a Happy New Year for 2013. The best way we found to thank you for supporting the Centreon project was to work hard over the Holidays Period to launch 3 new major versions of our main Open Source products including:

  • Centreon 2.4.0
  • Centreon Engine 1.3.0
  • Centreon Broker 2.4.0

As well as a new online documentation site.

Today, we are happy to introduce all these innovations to you.

Continue reading

Incoming search terms:

  • centreon graph widget

Centreon Engine & Centreon Broker – Technical and Performance Benchmarks

From Nagios©/NDO to Centreon Engine/Broker

Since a few years, the core of Nagios© has been maintained by a single developer and as a consequence has been evolving at a slower pace. The Nagios© community had attempted several times to broaden the developer base. Many community members such as Centreon Development team tried to propose improvements and patches, but with little success. Effective community commitment gradually deflated, long standing community supporters decided to fork Nagios© (among them are the people around Icinga for example), so did we!

 

To improve performance and quality, Centreon Engine and Centreon Broker have been created as a Nagios© alternative.

Thanks to many strategic partners, Merethis has tested Centreon Engine during every development steps. Centreon Engine is now stable and already run in production from small to medium IT networks. However, even if Centreon Engine and Centreon Broker are stable enough to deploy them in production, what about the performances? This study is based on a simple and common use case of production that compare a Nagios© based monitoring system to a Centreon Engine one. This aim of this study is not to reach the top of the Centreon Engine performances but just to compare it with Nagios© in a standard use case and show you the performances it brings. We have added the explanation of the biggest evolution Centreon developers did to make it easier to understand. We have planned to publish full performance benchmarks in the next months. If you want to give us your feedback on this document, the results, or the explanation, feel free to comment this blog post !

Key Comparison Findings

  • Centreon Engine and Centreon Broker start and are ready really faster than Nagios© working with NDO.
  • It gives the control back to the administrator faster and allows to restart with less loose of monitoring data.
  • Centreon Engine requires less CPU, less memory and decreases the number of IO.
  • Checks are done faster with less latency, and much more checks can be done with the same server.
  • Centreon need less powerful monitoring servers thanks to these improvements.
  • They can be run more easily on virtual machines, making the monitoring cloud simpler.

 

Next steps

More detailled benchmarks are already planned for full performance of Centreon Engine working with Broker. New improvements are already under development within Centreon Engine and Centreon Broker. Some of them for example in the 1.2 Centreon Engine should decrease the CPU activity more than it already does…

Want to know more?

Please, download the benchmarks : Centreon Engine Benchmarks
Stay tuned of the future releases by following us on twitter (@centreon) !
Download Centreon Engine and Centreon Broker

Centreon 2.3.5 and Centreon Broker 2.1.1 released today

We are glad to release 2 bugfix versions today

Before reading the changelog, please notice that if you want to upgrade to Centreon Broker 2.1 and further versions, you need to upgrade to Centreon 2.3.5 before because of a database change (see below for more details)

Centreon version 2.3.5

This version fix the following minor bugs :

  • fix the problem that occured when editing a service linked to an Host group from the service details page;
  • fix a problem with Nagios stats graphs;
  • fix nagiosPerfTrace running problems;
  • fix service categories special characters;
  • fix meta service parsing error;
  • fix problem with host downtime;
  • fix the pagination error in host and service downtime;
  • avoid to block SSH/SCP connexion in centcore;
  • fix the problem with the backup file in centstorage;
  • fix the generation of servicegroup dependancies which failed;
  • retrieve the status_file parameters in nagios.cfg;
  • delete the old Broker files when removing it.

Moreover, a few changes have been added :

  • it’s now possible to start Nagios from Administration » status screen;
  • Centreon Broker is now the default engine.

Centreon Broker 2.1 & 2.1.1

Centreon Broker 2.1 comes with a big database change:

  • The acknowledgements and downtimes delete time are thrown in databases;
  • Add the deletion_time column in the database table of the acknowledgements and downtimes.

The Centreon Broker 2.1.1 version just includes a small fix (issue on metrics names special chars).