Centreon 2.5.0 release

This post is also available in: French

After several weeks of waiting, we are pleased to announce the official release of Centreon 2.5.0.
This major release brings many diverse functional improvements to your Centreon system. Centreon 2.5.0 remains compatible with new up-coming release Broker 2.6, building on the success of the former release.

Find main novelties of this new version

   1. Implementation of configuration access control

Centreon’s mechanism of access control (ACL) was partly revised and, in particular, enhanced.
We decided to apply the same approach to configuration objects as for reading “real time” information, performance graphics and reporting. For example, upon a given user accessing the configuration objects, the user shall only be presented with a restricted view of those objects according to his attributed access rights.
The capacity to partition and delegate the supervision configuration to different teams according to their individual responsibilities, a long-awaited feature requested by many users, has finally been implemented!

For more information: http://blog.centreon.com/configuration-acl-centreon-2-5/?lang=fr

  2. Adding an internal notification system

A new integrated interface (UI) reporting system will allow you to quickly alert web-interface users of a change to any host or service status. This notification is implemented in two manners:
– opening a popup at the bottom of the screen
and / or
– emitting an arbitrary sound.

The user has the ability to activate both notification methods independently.

Being only a user configuration setting, each user is then able to customise his own sounds. All sounds are MP3s and are to be placed the Centreon server.

Therefore   – It’s up to you to choose whatever sound theme suits you!

For more information on this feature, go to the article

   3.  Enhanced SNMP trap handling

The internal sub-system has been thoroughly revised for the sake of improving system performance.
The first constraint was the capacity to handle increasingly large quantities of SNMP traps which has been achieved by the simplification of the number of components in the transformation chain.
No more SNMPTT component!
Centreon SNMP Manager now manages the entire process from snmptrapd to traps. The module has enhanced functionality, including the possibilities of either launching ordering PREEXEC or parallel processing. Additionally, there is now the possibility for each poller to have their own local database (sqllite) as opposed to having to access an external database ( open the TCP port (MySQL – 3306).
The pollers then become completely autonomous and can remain capable of handling traps offline.

For more information and to get the “best practices” of using this new system, check out our documentation : hhttp://documentation.centreon.com/docs/centreon/en/2.5.0/user/advanced/snmptrap.html

   4. Simplified configuration management of the host template order using drag’n’drop

Prior to this release, one had to re-enter all the same details to simply re-order the template precedence. This new release enables the user to merely drag’n’drop each individual element to its required position.

Updated

To update your Centreon system from version 2.4.x to 2.5.x. you must follow precisely the procedure below to ensure that there is no loss of performance graphs through the transition.
Of course, we also recommend that you make the usual backup of databases first.

The procedure is the following:

For installations based on CES-2.x, you will need to install php-pecl-json package before installing Centreon 2.5.0 packages :
# yum install php-pecl-json

If you use Centreon-Broker:

  • Make sure the Apache user has editing rights on the conf.pm file (no problems for servers running with Centreon Enterprise Server)
  • Stop the centreon-engine service on all of your pollers (including the central server)
  • Make sure that Centreon Broker has no more active retention or temporary files at large
  • Stop the centreon-broker services on your central servers
  • Update Centreon Broker (to version 2.6.0)
  • Restart Centreon Engine
  • Update Centreon (to version 2.5.0)
  • Run the changeRrDsName.pl script without arguments (located in /usr/share/centreon/bin for facilities CES)
  • Check the integrity of your various performance graphs  (View Menu> graphs)
  • Start Centreon-Broker
  • Re-start Centcore

If you use NDO:

  • Make sure the Apache user has editing rights on the conf.pm file (no problems for servers running with Centreon Enterprise Server)
  • Stop centstorage
  • Update Centreon (to version 2.5.0)
  • Run the changeRrDsName.pl script without arguments (located in /usr/share/centreon/bin for facilities CES)
  • Start centstorage
  • Re-start Centcore

The development team hopes this new Centreon release will bring entire satisfaction.
Tell us what you think!

Sneak preview, we wish to inform you that we are currently working on a new major version, 3.0, to be released in 2014.  We intend, with this version, to entirely rethink the design and bring greater enhancements to further facilitate the daily management of your IT systems.

So stay connected to the blog to keep up to date with the latest details about this future release !!

- article updated on February 19, 2014 -

Incoming search terms:

  • how to upgrade centreon 2 4

One thought on “Centreon 2.5.0 release

  1. Good afternoon,

    After updating my Centreon I can’t see the graphs of windows servers, exactly the graphs of cpu, memory and disk. These services use the “check_nt” command and the “check_nrpe” command.

    I uses the windows standar checks but I see this error log /var/log/centreon/centstorage.log

    2014-02-18 07:59:04 – Wrong perfdata format: physical memory %=71%;99;100 physical memory=2.8GB;3.9;3.94;0;3.94
    2014-02-18 07:59:04 – Wrong perfdata format: physical memory %=25%;99;100 physical memory=962.37MB;3801.05;3839.45;0;3839.45
    2014-02-18 07:59:04 – Wrong perfdata format: physical memory %=36%;99;100 physical memory=1.46GB;3.96;4;0;4
    2014-02-18 07:59:04 – Wrong perfdata format: G:\ Used Space=7,28Gb;17,00;18,00;0.00;20,00
    2014-02-18 07:59:04 – Wrong perfdata format: physical memory %=32%;99;100 physical memory=418.7MB;1266.69;1279.48;0;1279.48
    2014-02-18 07:59:04 – Wrong perfdata format: physical memory %=47%;99;100 physical memory=7.57GB;15.84;16;0;16
    2014-02-18 07:59:04 – Wrong perfdata format: physical memory %=59%;99;100 physical memory=1.19GB;1.98;2;0;2

    Best regards,

Leave a Reply