Áú»¢¶Ä²©

10 Virtual machine monitoring

Overview

Áú»¢¶Ä²© can use low-level discovery rules to automatically discover VMware hypervisors and virtual machines, and create hosts to monitor them based on pre-defined host prototypes.

Áú»¢¶Ä²© also includes ready-to-use templates for monitoring VMware vCenter or ESXi hypervisors.

The minimum required VMware vCenter or vSphere version is 5.1.

Data collection

Virtual machine monitoring consists of two steps:

1. Áú»¢¶Ä²© vmware collector processes collect virtual machine data - the processes obtain necessary information from VMware web services over the SOAP protocol, pre-process it, and store it in Áú»¢¶Ä²© server shared memory.

2. Áú»¢¶Ä²© poller processes retrieve data using Áú»¢¶Ä²© simple check VMware monitoring item keys.

Áú»¢¶Ä²© divides collected data into VMware configuration data and VMware performance counter data. Both types of data are collected independently by the vmware collector processes.

The following statistics are available based on the VMware performance counter information:

• Datastore
• Disk device
• CPU
• Power
• Network interface
• Custom performance counter items

For the complete list of items that obtain data from VMware performance counters, see VMware monitoring item keys.

Note that the frequency of VMware event retrieval depends on the polling interval of vmware.eventlog, but cannot be less then 5 seconds.

Configuration

If Áú»¢¶Ä²© server is compiled from sources, it must be compiled with the --with-libcurl --with-libxml2 configuration options to enable virtual machine monitoring. Áú»¢¶Ä²© packages are compiled with these options already enabled.

The following Áú»¢¶Ä²© server configuration file parameters can be modified for virtual machine monitoring:

• StartVMwareCollectors

• VMwareCacheSize
• VMwareFrequency
• VMwarePerfFrequency
• VMwareTimeout

Discovery

Áú»¢¶Ä²© can use low-level discovery rules (for example, vmware.hv.discovery[{$VMWARE.URL}]) to automatically discover VMware hypervisors and virtual machines. Moreover, Áú»¢¶Ä²© can use host prototypes to automatically generate real hosts for the discovered entities. For more information, see Host prototypes.

Configuration examples

For a basic example of how to set up Áú»¢¶Ä²© for monitoring VMware using the VMware FQDN template, see Monitor VMware with Áú»¢¶Ä²©.

For a more detailed example of how to create a host, a low-level discovery rule, and a host prototype for monitoring VMware, see Setup example.

Extended logging

The data collected by the vmware collector processes can be logged for detailed debugging using debug level 5. The debug level can be configured in the server and proxy configuration files or using the runtime control option -R log_level_increase="vmware collector,N", where "N" is the process number.

For example, to increase the debug level from 4 to 5 for all vmware collector processes, run the following command:

zabbix_server -R log_level_increase="vmware collector"

To increase the debug level from 4 to 5 for the second vmware collector process, run the following command:

zabbix_server -R log_level_increase="vmware collector,2"

When extended logging of VMware collector data is no longer required, it is recommended to decrease the debug level to default (3) by running the -R log_level_decrease command.

Troubleshooting

• In case of unavailable metrics, please ensure that they are not made unavailable or turned off by default in recent VMware vSphere versions, or if some limits are not placed on performance-metric database queries. For more information, see .
• If config.vpxd.stats.maxQueryMetrics is invalid or exceeds the maximum number of characters permitted error, add a config.vpxd.stats.maxQueryMetrics parameter to the vCenter Server settings. The value of this parameter should be the same as the value of maxQuerysize in VMware's web.xml file. For more information, see .
• If you suspect your Áú»¢¶Ä²© installation is using too much memory, see Profiling excessive memory usage with tcmalloc.