Installation and updates

Search for available packages

Centreon provides several Plugins Packs. To list all available Plugins Packs on your server, run the following command:

yum search ces-pack

Plugins Packs installation

Pack installation

First you have to install the set of Centreon templates provided by the Plugins Pack

Use the following command on the central server:

yum install ces-pack-$PLUGIN-PACK

Where $PLUGIN-PACK$ is the name of the Pack as listed by the yum search command.

Plugin installation

Then you have to install the necessary plugins referenced by the templates installed in the previous steps.

Use the following command on all pollers that will execute the checks:

yum install ces-plugins-$PLUGIN-PACK

Where $PLUGIN-PACK$ is the name of the Pack as listed by the yum search command.

Pack and Plugin updates

As plugins and packs are provided in RPM format, you can update them with usual rpm commands. If templates or check commands are modified, changes are automaticaly applied during the RPM update.


We’re doing our best to minimize the impact of updates. But sometimes, there are changes in the way plugins are called, like argument changes. This is reflected by updates in the associated check commands in the pack. Immediatly after the RPM updates, new plugins are executed by Engine, new templates and check commands are applied in Centreon configuration, BUT the old Engine configuration still refer to the old templates. That’s why it is safer to apply the procedure described below so as to reduce the impact of the update. In all cases, using a pre production is recommanded.

Plugins Packs update procedure:

First ensure you are using the last version of “Plugins Packs Manager” module. Follow the usual update procedure as for other modules, and make sure you are applying the update in Centreon module screen.

Then, you need to:

  1. update all packs on the central:

    # yum update ces-pack*
  2. as these changes will generate configuration updates (templates and commands changes), we need to deploy configuration of all pollers WITHOUT restarting them, as at this point the corresponding plugins are not yet updated

  3. stop Engine on all pollers

  4. update plugins on all pollers (including central) as they must all share the same version:

    # yum update ces-plugins*
  5. update plugin dependancies on all pollers (including central):

    # yum update centreon-plugins*
  6. restart Engine on all pollers to apply the new configuration deployed at step 2)

Then check you do not have new errors while executing new plugins.

Best practices

It is up to you to decide whether you install the plugins on all pollers, or only on the poller that will perform the checks. Keep in mind that if you do not install the plugin on one poller, you may have some errors if you decide one day to move a monitored host from one poller with the plugin to another poller that does not have this plugin. Moreover, if you update packs on the central, it is highly recommanded to also update associated plugins on the pollers, as some new checks are sometimes added in the packs, and won’t work if they do not have the corresponding command.

Plugins Packs management

Managing the installed plugins packs can be done through the web interface provided by the Plugins Packs Manager Centreon module.

Go to Administration > Modules > Plugin packs > Setup, you will the list of all the plugins packs installed on your server:


Each Plugins Pack displays the following information:

  • Version: version of the Plugin Pack
  • Release: version of the packaging of the Plugins Pack, matches the RPM version
  • Status: status of the pack, usually stable, but it may also have other values when the pack is still in test period, or when the pack is deprecated; an additionnal message is sometimes displayed as an icon giving more information
  • Number of host templates: list number of host templates provided by the Plugin Pack, click on the question mark to get the corresponding names
  • Number of service templates: list number of service templates provided by the Plugin Pack, click on the question mark to get the corresponding names
  • Number of commands: list number of commands provided by the Plugin Pack, click on the question mark to get the corresponding names
  • Actions: available actions on the Plugin Packs

You can click on the doc icon of a Plugin Pack to get help, this will open the documentation in a new window.

Deprecated packs management

During packs lifecycle, it may happen that packs are replaced by other packs. An old pack may then appear as “deprecated” in packs listing.


It is the client’s responsability to stay up to date regularly, as when a pack is marked as deprecated, it may stop working after a few months.