Skip to main content
Version: 23.10

Monitoring Connectors

As of April 2023, we're changing the names of some Centreon objects and attributes. "Monitoring Connectors" becomes the new name for Plugin Packs. We're making this change because users were often confused between two similar terms: Plugins and Plugin Packs, sometimes using one for the other. We're only changing the name! The functionality and capabilities stay the same.

A Monitoring Connector is a downloadable package containing a set of configuration templates that make it fast and easy to monitor your IT infrastructure. Applying a template from a Monitoring Connector is the easiest way to monitor a host.

Monitoring Connectors consist of 2 elements, which are installed separately:

  • A plugin that executes the monitoring commands from a poller. Plugins can be installed using the command line interface, or automatically.

  • 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 Monitoring Connectors with their respective monitoring procedures, please refer to the section on Monitoring Connectors.

Prerequisites​

Centreon Monitoring Connector Manager​

The Centreon Monitoring Connector 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:

dnf update centreon-pp-manager

License​

A license is required to access the full Monitoring Connectors catalog. Contact the Centreon support team to get your license.

Connectors​

Some Monitoring Connectors 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 Monitoring Connector. The connectors are included in the Monitoring Connectors license.

ConnectorDescription
NRPENRPE server, packaged by Centreon, with patches required to comply with Plugins Packs
NSClient++NSClient++, packaged by Centreon, ready to use with embedded Centreon Plugins
VMWarePerl daemon using VMware SDK to monitor VMware platforms
AS400Java-based connector allowing you to execute checks on an AS400

Installing a Monitoring Connector​

Installing a Monitoring Connector is a 4-step process:

  1. Accessing the Monitoring Connectors catalog.
  2. Installing the pack.
  3. Checking the monitoring procedure.
  4. Installing the plugin.

Accessing the Monitoring Connectors catalog​

  • If you have an online license, the Monitoring Connectors catalog is already available on your platform, on the Configuration > Monitoring Connector Manager page.

  • If you have an offline license:

    • install the Monitoring Connectors repository (go to the Centreon support portal for its address)
    • install or update the Monitoring Connectors catalog from your Centreon Central server:
dnf install centreon-pack-*

or:

dnf update centreon-pack-*

Please note that although this command is called install, it only makes Monitoring Connectors available in the Centreon interface. It will not install the Monitoring Connectors themselves. Please follow the rest of the procedure.

Installing the pack​

You now have access to the Monitoring Connectors catalog, on page Configuration > Monitoring Connector Manager:

image

To install a pack, hover over the icon with the mouse and click the +

image

You can also click the Monitoring Connector to display more details and click the +

image

Once the pack is installed, it has a green outline and a green check mark.

Before installationAfter installation
imageimage

Managing dependencies​

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 version 18.10.x:

image

Checking the monitoring procedure​

Some Monitoring Connectors 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 the i icon of each pack to access its documentation:

image

Installing the plugin​

Plugins can be installed from the command line or automatically.

Automatic installation​

  1. Install the pack.
  2. Check the monitoring procedure for extra configuration steps.
  3. On the Configuration > Monitoring Connector Manager page, set Automatic installation of plugins to ON.
  4. Use a template provided by the pack to monitor a host or a service.
  5. Deploy the configuration for the pollers that monitor these hosts or services: the corresponding plugins will be automatically installed on these pollers.

Manual installation​

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:

dnf install centreon-plugin-$PLUGIN-PACK$

Where $PLUGIN-PACK$ is the name of the pack. Example:

dnf install centreon-plugin-Cloud-Aws-Ec2-Api

Using Monitoring Connectors​

Apply a template from a Monitoring Connector to a host or service to start monitoring it:

  1. Create the host/the service, and in the Template(s) field, choose the template for the Monitoring Connector you want.

  2. Deploy the configuration.

Updating Monitoring Connectors​

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 Monitoring Connector, it means that an update is available.

image

Hover over the Monitoring Connector and click the arrow,

image

or click the Monitoring Connector to display more details, and then click the arrow.

image

Confirm the update.

image

Your pack is up to date. You can now update the plugin.

image

To update all packs:

You can also update all the packs at the same time: when pack updates are available, an Update all button appears. Note that you will still have to update the plugins.

image

Updating the plugins​

On the Configuration > Monitoring Connector Manager page, if Automatic installation of plugins is set to ON, plugins will be updated automatically when you deploy the configuration for a poller that monitors a host that uses these plugins.

If Automatic installation of plugins is set to OFF, use the following command to update the plugins:

  1. Execute the following command on all pollers:
dnf update centreon-plugin\*

  1. Deploy the configuration for all pollers. The Restart Monitoring Engine option must be set to Restart.

  2. 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 update them on each poller also.

Uninstalling Monitoring Connectors​

As with installation, you can remove a pack either by hovering over the desired pack in the UI and clicking on the red cross:

image

or by clicking first the pack and then the red cross:

image

Confirm the uninstallation.

image

Your Monitoring Connector is now uninstalled.

image

Managing dependencies​

You will not be able remove a pack if host and service templates created by the Monitoring Connector are being used by any monitored hosts and services.

image

To uninstall the pack you will need to either:

  • delete the hosts and services linked to the templates provided by the Monitoring Connector,
  • 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.