Skip to main content

VMware VM

VMware provides cloud computing and virtualization software.

The Centreon VMware VM Monitoring Connector relies on a dedicated connector (centreon-vmware-daemon) that uses the VMware SDK to send requests to the vCenter's API. It allows you to monitor VMware virtual machines.

Pack assets​

Templates​

The Monitoring Connector VMware VM brings a host template:

  • Virt-VMWare2-VM-custom

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

Service AliasService TemplateService Description
Vm-LimitVirt-VMWare2-Vm-Limit-Generic-customCheck limit definition.
Vm-SnapshotVirt-VMWare2-Vm-Snapshot-Generic-customCheck the age of the snapshot for a virtual machine.
Vm-StatusVirt-VMWare2-Vm-Status-Generic-customCheck global status of a virtual machine.
Vm-ThinprovisioningVirt-VMWare2-Vm-Thinprovisioning-Generic-customCheck if a virtual machine has a disk in mode 'thin provisioning' or not.
Vm-ToolsVirt-VMWare2-Vm-Tools-Generic-customCheck the state of vmtools for a virtual machine.

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

Discovery rules​

Host discovery​

Rule nameDescription
VMWare VMDiscover VMWare virtual machines

More information about discovering hosts automatically is available on the dedicated page.

Collected metrics & status​

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

Metric nameUnit
vm~statusN/A
vm~vm.cpu.utilization.percentage%
vm~vm.cpu.utilization.mhzMHz
vm~vm.cpu.ready.percentage%
vm~cpu#vm.core.cpu.utilization.percentageMHz

To obtain this new metric format, include --use-new-perfdata in the EXTRAOPTIONS service macro.

Prerequisites​

Centreon VMware daemon​

To monitor VMWare resources, Centreon uses a daemon to connect to and send requests to the vCenter (or the ESX, but it is recommended to use the vCenter).

Install this daemon on each needed poller:

apt install centreon-plugin-virtualization-vmware-daemon

Go to Configuration > Additional connector configuration to configure the connection to your vCenter.

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".

Tags and custom attributes​

To discover tags and custom attributes, you must :

  • use version 3.2.5 of centreon-vmware-daemon
  • add --tags in the additional discovery options: go to the Configuration > Hosts > Discovery page, and to the 3rd step (Set discovery parameters), in the section Additional parameters, in the Additional options field, type --tags.

Network flows​

The Centreon poller (with the VMWare daemon installed on it) needs to access the vCenter using HTTPS (TCP/443).

If several pollers use the same daemon, then they must access the poller that has the VMware daemon installed on it using TCP/5700.

Installing the monitoring connector​

Pack​

  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-vm
  1. Whatever the license type (online or offline), install the VMware VM connector through the Configuration > Monitoring Connectors Manager menu.

Plugin​

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-VM-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
CENTREONVMWAREPORTPort of the daemon (default: 5700)5700
CENTREONVMWARECONTAINERContainer to use (it depends on the daemon's configuration)default
CENTREONVMWAREHOSTHostname of the server on which the daemon is installed (required)localhostX
VMNAMEName of the VM to check. If not defined, all VMs will be checked.
VMUUIDSpecify the VM's UUID
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
UNKNOWNSTATUSDefine the conditions to match for the status to be UNKNOWN (Default: '%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection_state}, %{power_state}%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i
WARNINGCPUWarning threshold
CRITICALCPUCritical threshold
WARNINGREADYWarning threshold5
CRITICALREADYCritical threshold10
WARNINGSTATUSDefine the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection_state}, %{power_state}
CRITICALSTATUSDefine the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection_state}, %{power_state}
WARNINGUSAGEWarning threshold80
CRITICALUSAGECritical threshold90
WARNINGUSAGEMHZWarning threshold
CRITICALUSAGEMHZCritical threshold
EXTRAOPTIONSAny extra option you may want to add to the command (e.g. a --verbose flag). All options are listed here
  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/centreon_vmware_connector_client.pl \
    --plugin=apps::vmware::connector::plugin \
    --mode=swap-vm \
    --custommode=connector \
    --connector-hostname='localhost' \
    --connector-port='5700' \
    --container='default'  \
    --vm-hostname='' \
    --filter-uuid='' \
    --unknown-status='%{connection_state} !~ /^connected$/i or %{power_state}  !~ /^poweredOn$/i' \
    --warning-status='' \
    --critical-status='' \
    --warning-swap-in='' \
    --critical-swap-in=''  \
    --warning-swap-out='' \
    --critical-swap-out=''

The expected command output is shown below:

OK: All virtual machines are ok | '*vm*#vm.swap.in.usage.bytespersecond'=B/s;;;0;'*vm*#vm.swap.out.usage.bytespersecond'=B/s;;;0;

Troubleshooting​

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/centreon_vmware_connector_client.pl \
    --plugin=apps::vmware::connector::plugin \
    --list-mode

The plugin brings the following modes:

ModeLinked service template
alarm-datacenter [code]Not used in this Monitoring Connector
alarm-host [code]Not used in this Monitoring Connector
countvm-host [code]Not used in this Monitoring Connector
cpu-cluster [code]Not used in this Monitoring Connector
cpu-host [code]Not used in this Monitoring Connector
cpu-vm [code]Virt-VMWare2-Vm-Cpu-Generic-custom
datastore-countvm [code]Not used in this Monitoring Connector
datastore-host [code]Not used in this Monitoring Connector
datastore-io [code]Not used in this Monitoring Connector
datastore-iops [code]Not used in this Monitoring Connector
datastore-snapshot [code]Not used in this Monitoring Connector
datastore-usage [code]Not used in this Monitoring Connector
datastore-vm [code]Virt-VMWare2-Vm-Datastores-Iops-Generic-custom
device-vm [code]Virt-VMWare2-Vm-Device-Generic-custom
discovery [code]Used for host discovery
getmap [code]Not used in this Monitoring Connector
health-host [code]Not used in this Monitoring Connector
licenses [code]Not used in this Monitoring Connector
limit-vm [code]Virt-VMWare2-Vm-Limit-Generic-custom
list-clusters [code]Not used in this Monitoring Connector
list-datacenters [code]Not used in this Monitoring Connector
list-datastores [code]Not used in this Monitoring Connector
list-nichost [code]Not used in this Monitoring Connector
maintenance-host [code]Not used in this Monitoring Connector
memory-host [code]Not used in this Monitoring Connector
memory-vm [code]Virt-VMWare2-Vm-Memory-Generic-custom
net-host [code]Not used in this Monitoring Connector
net-vm [code]Not used in this Monitoring Connector
service-host [code]Not used in this Monitoring Connector
snapshot-vm [code]Virt-VMWare2-Vm-Snapshot-Generic-custom
stat-connectors [code]Not used in this Monitoring Connector
status-cluster [code]Not used in this Monitoring Connector
status-host [code]Not used in this Monitoring Connector
status-vm [code]Virt-VMWare2-Vm-Status-Generic-custom
storage-host [code]Not used in this Monitoring Connector
swap-host [code]Not used in this Monitoring Connector
swap-vm [code]Virt-VMWare2-Vm-Swap-Generic-custom
thinprovisioning-vm [code]Virt-VMWare2-Vm-Thinprovisioning-Generic-custom
time-host [code]Not used in this Monitoring Connector
tools-vm [code]Virt-VMWare2-Vm-Tools-Generic-custom
uptime-host [code]Not used in this Monitoring Connector
vmoperation-cluster [code]Not used in this Monitoring Connector
vsan-cluster-usage [code]Not used in this Monitoring Connector

Available options​

Generic options​

All generic options are listed here:

OptionDescription
--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-perfdataKeep only 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. Example: 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 the vpshere/ESX instance to connect to.
--vsphere-usernameUsername to use to connect to the vpshere/ESX instance (with --vsphere-address).
--vsphere-passwordPassword used to connect to the vpshere/ESX instance (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 from 300 or 20.
--time-shiftCan shift the time. With the following option you can average X counters values (default: 0).
--case-insensitiveSearches 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:

OptionDescription
--vm-hostnameHostname of the VM to check. If not set, we check all VMs.
--filterDefine which VMs should be monitored based on their names. This option will be treated as a regular expression.
--filter-descriptionDefine which VMs should be monitored based on their description. This option will be treated as a regular expression.
--filter-osDefine which VMs should be monitored based on their OS. This option will be treated as a regular expression.
--scope-datacenterSearch in the following datacenter(s) (can be a regexp).
--scope-clusterSearch in the following cluster(s) (can be a regexp).
--scope-hostSearch in the following host(s) (can be a regexp).
--unknown-statusDefine the conditions to match for the status to be UNKNOWN (Default: '%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i'). You can use the following variables: %{connection_state}, %{power_state}
--warning-statusDefine the conditions to match for the status to be WARNING (Default: ''). You can use the following variables: %{connection_state}, %{power_state}
--critical-statusDefine the conditions to match for the status to be CRITICAL (Default: ''). You can use the following variables: %{connection_state}, %{power_state}
--warning-*Warning threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'.
--critical-*Critical threshold. Can be: 'total-cpu', 'total-cpu-mhz', 'cpu-ready', 'cpu'.

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

/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \
    --plugin=apps::vmware::connector::plugin \
    --mode=swap-vm \
    --help