A Plugin Pack is a downloadable package containing a set of configuration templates that make it fast and easy to monitor your IT infrastructure. Applying a Plugin Pack is the easiest way to monitor a host.
Plugin Packs consist of 2 elements, which are installed separately:
A plugin that executes the monitoring commands from a poller. Plugins are installed using the command line interface.
A pack that contains commands, host templates and service templates. Packs are installed via the Centreon interface. For each type of equipment, the templates determine which indicators will be monitored and set default warning and critical thresholds (these may be fine-tuned later on).
Some packs also contain discovery rules.
To get an up-to-date list of all Plugin Packs with their respective monitoring procedure, please refer to the section on Plugin Packs.
Centreon Plugin Pack Manager
The Centreon Plugin Pack Manager module can install, update or remove Plugin Packs. It is installed by default. We recommend that you keep this module regularly updated.
To update this module, run the following command:
yum update centreon-pp-manager
Some Plugin Packs also require a Connector (e.g. AS400, VMWare) or an agent (e.g. Windows NRPE). In that case, it is explained in the monitoring procedure for the Plugin Pack. The connectors are included in the Plugin Packs license.
|NRPE||NRPE server, packaged by Centreon, with patches required to comply with Plugins Packs|
|NSClient++||NSClient++, packaged by Centreon, ready to use with embedded Centreon Plugins|
|VMWare||Perl daemon using VMware SDK to monitor VMware platforms|
|AS400||Java-based connector allowing you to execute checks on an AS400|
Installing a Plugin Pack
Installing a plugin pack is a 4-step process:
- Accessing the Plugin Packs catalog.
- Installing the pack.
- Checking the monitoring procedure.
- Installing the plugin.
Accessing the Plugin Packs catalog
If you have an online license, the Plugin Packs catalog is already available on your platform, on page Configuration > Plugin Packs.
If you have an offline license:
install the Plugin Packs repository (contact the Centreon support team for its address)
install or update the Plugin Packs catalog from your Centreon Central server:
yum install centreon-pack-*
yum update centreon-pack-*
Please note that although this command is called
install, it only makes Plugin Packs available in the Centreon interface. It will not install the Plugin Packs themselves. Please follow the rest of the procedure.
Installing the pack
You now have access to the Plugin Packs catalog, on page Configuration > Plugin Packs:
To install a pack, hover over the icon with the mouse and click on the
You can also click on the Plugin Pack to display more details and click on the
Once the pack is installed, it has a green outline and a green check mark.
|Before installation||After installation|
During installation, some objects in the pack may not be installed. These objects are often additional configuration objects and are not required to deploy the configuration templates provided by the pack.
Most of the time, it is necessary to update your Centreon platform and then reinstall your pack.
In the following example, the "autodiscover" object is a discovery rule for the "Centreon Auto Discovery" module, but this one is only available for Centreon in 18.10.x version:
Checking the monitoring procedure
Some Plugin Packs require extra configuration steps. Read the monitoring procedure for each installed pack
to understand the contents of the pack and to find out about any prerequisites. Click on the
i icon of each pack to access its documentation:
Installing the plugin
The monitoring procedure contains an Installation section that explains how to install the plugin (with an online or an offline license). Install the plugin on each poller that will execute the plugin checks.
The installation command looks like this:
yum install centreon-plugin-$PLUGIN-PACK$
$PLUGIN-PACK$ is the name of the pack. Example:
yum install centreon-plugin-Cloud-Aws-Ec2-Api
Bear in mind that the
yumcommand is case-sensitive.
Using plugin packs
Apply a plugin pack to a host or service to start monitoring them:
Create the host/the service, and in the Template(s) field, choose the template for the Plugin Pack you want.
Deploy the configuration.
Updating Plugin Packs
You need to update both the plugin and the pack.
Updating one pack/all packs
To update one pack:
If an arrow appears on a Plugin Pack it means that an update is available.
Hover over the Plugin Pack and click on the arrow,
or click on the Plugin Pack to display more details, then click on the arrow.
Confirm the update.
Your pack is up to date. You can now update the plugin.
To update all packs:
You can also update all packs in one go: when pack updates are available, an Update all button appears. Note that you will still have to update the plugins.
Updating the plugins
To update the plugins:
Execute the following command on all pollers:
yum update centreon-plugins\*
Deploy the configuration for all pollers. The Restart Monitoring Engine option must be set to Restart.
Check that you do not have new errors while executing new plugins.
It is your choice whether to install all the plugins on every poller, or just the required plugins. Keep in mind that you may encounter errors if you migrate a monitored host to a poller that happens to be missing the necessary plugins. If you update the plugins on the Centreon central server, be sure to also update them on each poller.
Uninstalling Plugin Packs
As with installation, you can remove a pack either by hovering over the desired pack in the UI and clicking on the red cross:
or by clicking first on the pack and then on the red cross:
Confirm the uninstallation.
Your Plugin Pack is now uninstalled.
You will not be able remove a pack if host and service templates created by the Plugin Pack are being used by any monitored hosts and services.
To uninstall the pack you will need either to:
- delete the hosts and services linked to the templates provided by the Plugin Pack,
- or unlink the hosts and services from the corresponding templates.
Attempting to uninstall a pack that is a dependency of another pack will cause the uninstallation process to stop if the pack or its dependency is used by any hosts and services. Otherwise, the pack and its dependencies can be removed.