Skip to main content

VMware vCenter

VMWare provides cloud computing and virtualization software and services.

The Centreon Plugins and Monitoring Connectors rely on the Centreon VMWare Connector to request the vCenter API.

With this connector, Centreon can monitor VMs, Datastores, ESXs, Clusters, etc.

This Monitoring Connector can be used with either version 6 or 7 of the VMware API.

Pack assets


The Monitoring Connector VMware vCenter brings a host template:

  • Virt-VMWare2-VCenter-custom

The connector brings the following service templates (sorted by the host template they are attached to):

Service AliasService TemplateService Description
Vm-Tools-GlobalVirt-VMWare2-Vm-Tools-Global-customCheck vmtools state of multiple virtual machines

The services listed above are created automatically when the Virt-VMWare2-VCenter-custom host template is used.

Discovery rules

Service discovery

Rule nameDescription

More information about discovering services automatically is available on the dedicated page and in the following chapter.

Collected metrics & status

Here is the list of services for this connector, detailing all metrics linked to each service.

Metric nameUnit


Centreon VMWare Connector

For the VMWare monitoring, Centreon use daemon to connect and request the vCenter.

Install this daemon on each needed poller:

yum install centreon-plugin-Virtualization-VMWare-daemon

To configure the access to your infrastructure, edit the "/etc/centreon/" configuration file:

%centreon_vmware_config = (
vsphere_server => {
default => {
url => 'https://<ip_hostname>/sdk',
username => '<username>',
password => '<password>'


Make sure to replace variables with needed information:

  • ip_hostname: IP address or hostname of the vCenter or ESX (if standalone),
  • username: username with at least "read only" access to the vCenter or ESX (you can use domain user),
  • password: password of the username.

You can configure multiple vCenter or ESXi connections using this structure:

%centreon_vmware_config = (
vsphere_server => {
'my_first_vcenter' => {
url => 'https://<ip_hostname>/sdk',
username => '<username>',
password => '<password>'
'my_other_vcenter' => {
url => 'https://<ip_hostname>/sdk',
username => '<DOMAIN>\<username>',
password => '<password>'
port => 5700


Each entry is called a container.

You can also define the "port" attribute to change listening port.

Then start the daemon and make sure it is configured to start at server boot:

systemctl start centreon_vmware
systemctl enable centreon_vmware

Make sure that the daemon configuration works fine by looking for errors in "/var/log/centreon/centreon_vmware.log".

Network flows

The Poller with the Centreon VMware Connector installed need to access in TCP/443 HTTPS to the vCenter.

The Pollers that request the Centreon VMWare Connector host need to access in TCP/5700 to the Centreon VMWare Connector host.

Installing the monitoring connector


  1. If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Monitoring Connectors Manager menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
dnf install centreon-pack-virtualization-vmware2-vcenter-generic
  1. Whatever the license type (online or offline), install the VMware vCenter connector through the Configuration > Monitoring Connectors Manager menu.


Since Centreon 22.04, you can benefit from the 'Automatic plugin installation' feature. When this feature is enabled, you can skip the installation part below.

You still have to manually install the plugin on the poller(s) when:

  • Automatic plugin installation is turned off
  • You want to run a discovery job from a poller that doesn't monitor any resource of this kind yet

More information in the Installing the plugin section.

Use the commands below according to your operating system's package manager:

dnf install centreon-plugin-Virtualization-Vmware2-Connector-Plugin

Using the monitoring connector

Using a host template provided by the connector

  1. Log into Centreon and add a new host through Configuration > Hosts.
  2. Fill the Name, Alias & IP Address/DNS fields according to your ressource settings.
  3. Apply the Virt-VMWare2-VCenter-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
  4. Fill in the macros you want. Some macros are mandatory.
MacroDescriptionDefault valueMandatory
CENTREONVMWAREPORTConnector port (default: 5700)5700
CENTREONVMWARECONTAINERContainer to use (it depends on the connector's configuration)default
CENTREONVMWAREHOSTConnector hostname (required)localhost
CENTREONVMWAREEXTRAOPTIONSAny extra option you may want to add to every command (e.g. a --verbose flag). All options are listed here
  1. Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.

Using a service template provided by the connector

  1. If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
  2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).
MacroDescriptionDefault valueMandatory
EXTRAOPTIONSAny extra option you may want to add to the command (e.g. a --verbose flag). All options are listed here--verbose
  1. Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.

How to check in the CLI that the configuration is OK and what are the main options for?

Once the plugin is installed, log into your Centreon poller's CLI using the centreon-engine user account (su - centreon-engine). Test that the connector is able to monitor a resource using a command like this one (replace the sample values by yours):

/usr/lib/centreon/plugins/ \
--plugin=apps::vmware::connector::plugin \
--mode=vsan-cluster-usage \
--custommode=connector \
--connector-hostname='localhost' \
--connector-port='5700' \
--container='default' \
--cluster-name='.*' \
--filter \
--warning-backend-read-usage='' \
--critical-backend-read-usage='' \
--warning-backend-write-usage='' \
--critical-backend-write-usage='' \
--warning-backend-congestions='' \
--critical-backend-congestions='' \
--warning-backend-outstanding-io='' \
--critical-backend-outstanding-io='' \
--warning-backend-throughput-read='' \
--critical-backend-throughput-read='' \
--warning-backend-throughput-write='' \
--critical-backend-throughput-write='' \
--warning-backend-latency-read='' \
--critical-backend-latency-read='' \
--warning-backend-latency-write='' \

The expected command output is shown below:

OK: All clusters are ok | '*cluster*'=iops;;;0;'*cluster*#cluster.vsan.backend.write.usage.iops'=iops;;;0;'*cluster*#cluster.vsan.backend.congestions.count'=;;;0;'*cluster*'=;;;0;'*cluster*'=B/s;;;0;'*cluster*#cluster.vsan.backend.throughput.write.bytespersecond'=B/s;;;0;'*cluster*'=ms;;;0;'*cluster*#cluster.vsan.backend.latency.write.milliseconds'=ms;;;0;

Here is another example:

/usr/lib/centreon/plugins// \
--plugin=apps::vmware::connector::plugin \
--mode=snapshot-vm \
--custommode=connector \
--connector-hostname='localhost' \
--connector-port='5700' \
--container='vcenter01' \
--vm-hostname='.*' \
--filter \
--filter-uuid='' \
--warning='259200' \
--critical='432000' \
--disconnect-status='ok' \
--nopoweredon-skip \
--check-consolidation \

The expected output is shown below:

CRITICAL: Snapshots for VM older than 432000 seconds: [TLS-LIN-001] | 'num_warning'=0;;;0; 'num_critical'=1;;;0;
'TLS-LIN-001' snapshot create time: 2020-07-20T12:19:16.246902Z [only base os image]


Please find the troubleshooting documentation for Centreon Plugins typical issues.

Available modes

In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. However, you will need to specify the correct mode for the template if you want to test the execution command for the connector in your terminal.

All available modes can be displayed by adding the --list-mode parameter to the command:

/usr/lib/centreon/plugins/ \
--plugin=apps::vmware::connector::plugin \

The plugin brings the following modes:

ModeLinked service template
alarm-datacenter [code]Virt-VMWare2-Datacenter-Alarms-Generic-custom
alarm-host [code]Virt-VMWare2-ESX-Alarms-Global-custom
countvm-host [code]Virt-VMWare2-ESX-Vm-Count-Global-custom
cpu-cluster [code]Virt-VMWare2-Cluster-Cpu-Generic-custom
cpu-host [code]Virt-VMWare2-ESX-Cpu-Global-custom
cpu-vm [code]Virt-VMWare2-Vm-Cpu-Global-custom
datastore-countvm [code]Virt-VMWare2-Datastore-Vm-Count-Global-custom
datastore-host [code]Virt-VMWare2-ESX-Datastores-Latency-Global-custom
datastore-io [code]Virt-VMWare2-Datastore-Io-Global-custom
datastore-iops [code]Virt-VMWare2-Datastore-Iops-Global-custom
datastore-snapshot [code]Virt-VMWare2-Datastore-Snapshots-Global-custom
datastore-usage [code]Virt-VMWare2-Datastore-Usage-Global-custom
datastore-vm [code]Virt-VMWare2-Vm-Datastores-Iops-Global-custom
device-vm [code]Virt-VMWare2-Vm-Device-Global-custom
discovery [code]Not used in this Monitoring Connector
getmap [code]Not used in this Monitoring Connector
health-host [code]Virt-VMWare2-ESX-Health-Global-custom
licenses [code]Virt-VMWare2-Licenses-custom
limit-vm [code]Virt-VMWare2-Vm-Limit-Global-custom
list-clusters [code]Used for service discovery
list-datacenters [code]Used for service discovery
list-datastores [code]Used for service discovery
list-nichost [code]Not used in this Monitoring Connector
maintenance-host [code]Virt-VMWare2-ESX-Maintenance-Global-custom
memory-host [code]Virt-VMWare2-ESX-Memory-Global-custom
memory-vm [code]Virt-VMWare2-Vm-Memory-Global-custom
net-host [code]Virt-VMWare2-ESX-Traffic-Global-custom
net-vm [code]Not used in this Monitoring Connector
service-host [code]Virt-VMWare2-ESX-Service-Global-custom
snapshot-vm [code]Virt-VMWare2-Vm-Snapshot-Global-custom
stat-connectors [code]Not used in this Monitoring Connector
status-cluster [code]Virt-VMWare2-Cluster-Status-Generic-custom
status-host [code]Virt-VMWare2-ESX-Status-Global-custom
status-vm [code]Virt-VMWare2-Vm-Status-Global-custom
storage-host [code]Virt-VMWare2-ESX-Storage-Global-custom
swap-host [code]Virt-VMWare2-ESX-Swap-Global-custom
swap-vm [code]Virt-VMWare2-Vm-Swap-Global-custom
thinprovisioning-vm [code]Virt-VMWare2-Vm-Thinprovisioning-Global-custom
time-host [code]Virt-VMWare2-ESX-Time-Global-custom
tools-vm [code]Virt-VMWare2-Vm-Tools-Global-custom
uptime-host [code]Virt-VMWare2-ESX-Uptime-Global-custom
vmoperation-cluster [code]Not used in this Monitoring Connector
vsan-cluster-usage [code]Virt-VMWare2-Vsan-Cluster-Usage-Generic-custom

Available options

Generic options

All generic options are listed here:

--modeDefine the mode in which you want the plugin to be executed (see--list-mode).
--dyn-modeSpecify a mode with the module's path (advanced).
--list-modeList all available modes.
--mode-versionCheck minimal version of mode. If not, unknown error.
--versionReturn the version of the plugin.
--custommodeWhen a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option.
--list-custommodeList all available custom modes.
--multipleMultiple custom mode objects. This may be required by some specific modes (advanced).
--pass-managerDefine the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass.
--verboseDisplay extended status information (long output).
--debugDisplay debug messages.
--filter-perfdataFilter perfdata that match the regexp. Eg: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data.
--filter-perfdata-advFilter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Eg: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value.
--explode-perfdata-maxCreate a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '_max' suffix). Eg: it will split 'used_prct'=26.93%;0:80;0:90;0;100 into 'used_prct'=26.93%;0:80;0:90;0;100 'used_prct_max'=100%;;;;
--change-perfdata --extend-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[newuom],[min],[m ax]] Common examples: Convert storage free perfdata into used: --change-perfdata=free,used,invert() Convert storage free perfdata into used: --change-perfdata=used,free,invert() Scale traffic values automatically: --change-perfdata=traffic,,scale(auto) Scale traffic values in Mbps: --change-perfdata=traffic_in,,scale(Mbps),mbps Change traffic values in percent: --change-perfdata=traffic_in,,percent()
--extend-perfdata-groupAdd new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation[,[ne wuom],[min],[max]] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets_wrong,sum(packets_(discard |error)_(in|out))' Sum traffic by interface: --extend-perfdata-group='traffic_in_(.*),traffic_$1,sum(traf fic_(in|out)_$1)'
--change-short-output --change-long-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern~replacement~modifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Eg: adding --change-short-output='OK~Up~gi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-exitReplace an exit code with one of your choice. Eg: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state.
--range-perfdataRewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata.
--filter-uomMask the units when they don't match the given regular expression.
--opt-exitReplace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown.
--output-ignore-perfdataRemove all the metrics from the service. The service will still have a status and an output.
--output-ignore-labelRemove the status label ("OK:", "WARNING:", "UNKNOWN:", CRITICAL:") from the beginning of the output. Eg: 'OK: Ram Total:...' will become 'Ram Total:...'
--output-xmlReturn the output in XML format (to send to an XML API).
--output-jsonReturn the output in JSON format (to send to a JSON API).
--output-openmetricsReturn the output in OpenMetrics format (to send to a tool expecting this format).
--output-fileWrite output in file (can be combined with json, xml and openmetrics options). E.g.: --output-file=/tmp/output.txt will write the output in /tmp/output.txt.
--disco-formatApplies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML).
--disco-showApplies only to modes beginning with 'list-'. Returns the list of discovered objects (formatted in XML) for service discovery.
--float-precisionDefine the float precision for thresholds (default: 8).
--source-encodingDefine the character encoding of the response sent by the monitored resource Default: 'UTF-8'.
--connector-hostnameConnector hostname (required).
--connector-portConnector port (default: 5700).
--containerContainer to use (it depends on the connector's configuration).
--vsphere-addressAddress of vpshere/ESX to connect.
--vsphere-usernameUsername of vpshere/ESX connection (with --vsphere-address).
--vsphere-passwordPassword of vpshere/ESX connection (with --vsphere-address).
--timeoutSet global execution timeout (Default: 50)
--sampling-periodChoose the sampling period (can change the default sampling for counters). Should be not different than 300 or 20.
--time-shiftCan shift the time. We the following option you can average X counters values (default: 0).
--case-insensitiveSearchs are case insensitive.
--unknown-connector-statusSet unknown threshold for connector status (Default: '%{code} \< 0 || (%{code} > 0 && %{code} \< 200)'). You can use the following variables: %{code}, %{short_message}, %{extra_message}.
--warning-connector-statusSet warning threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short_message}, %{extra_message}.
--critical-connector-statusSet critical threshold for connector status (Default: ''). You can use the following variables: %{code}, %{short_message}, %{extra_message}.

Modes options

All available options for each service template are listed below:

--cluster-namecluster to check. If not set, we check all clusters.
--filterCluster name is a regexp.
--scope-datacenterSearch in following datacenter(s) (can be a regexp).
--warning- --critical-Thresholds. Can be: 'total-cpu', 'total-cpu-mhz'.

All available options for a given mode can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/ \
--plugin=apps::vmware::connector::plugin \
--mode=vsan-cluster-usage \