documentation
Public
Source
xxxxxxxxxx- 若`config.vpxd.stats.maxQueryMetrics`无效或者超出了允许字符错误的最大阈值，那么用户可以通过添加一个`config.vpxd.stats.maxQueryMetrics`参数到vCenter Server 配置中来解决这个问题。该参数的值应于VMware *web.xml*文档中`maxQuerysize`的值相同。更多的信息，请查阅[*VMware Knowledge Base* article](https://kb.vmware.com/s/article/2107096)。</target><?xml version='1.0' encoding='UTF-8'?><xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2"> <file source-language="en" target-language="zh-CN" datatype="plaintext" original="manual/vm_monitoring.md"> <body> <trans-unit id="3ca85094" xml:space="preserve"> <source># 10 Virtual machine monitoring</source> <target># 10. 虚拟机监控</target> </trans-unit> <trans-unit id="621e23e6" xml:space="preserve"> <source>#### OverviewZabbix can use [low-level discovery](/manual/discovery/low_level_discovery) rules to automatically discover VMware hypervisors and virtual machines,and create hosts to monitor them based on pre-defined [host prototypes](/manual/discovery/low_level_discovery/host_prototypes).Zabbix also includes [ready-to-use templates](/manual/config/templates_out_of_the_box/vmware) for monitoring VMware vCenter or ESXi hypervisors.The minimum required VMware vCenter or vSphere version is 5.1.</source> <target state="needs-translation">#### 概述Zabbix可以使用[低级别发现规则](/manual/discovery/low_level_discovery)自动发现VMware hypervisors（宿主机）和virtual machines（虚拟机），并根据预定义的[主机原型](/manual/discovery/low_level_discovery/host_prototypes)创建监控主机来完成监控功能。在Zabbix中同样包含多个现成的监控模板用于监控VMware vCenter 或者 ESXi hypervisors。截至目前为止，支持监控的VMware vCenter或vSphere 版本为5.1版。</target> </trans-unit> <trans-unit id="4c2e8939" xml:space="preserve"> <source>#### Data collectionVirtual machine monitoring consists of two steps:1. Zabbix *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 Zabbix server shared memory.2. Zabbix *poller* processes retrieve data using Zabbix simple check [VMware monitoring item keys](/manual/vm_monitoring/vmware_keys).Zabbix 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 itemsFor the complete list of items that obtain data from VMware performance counters, see [*VMware monitoring item keys*](/manual/vm_monitoring/vmware_keys#footnotes).Note that the frequency of VMware event retrieval depends on the polling interval of [vmware.eventlog](/manual/vm_monitoring/vmware_keys#vmware.eventlog), but cannot be less then 5 seconds.</source> <target>#### 数据采集虚拟机的监控包含两个步骤：1. Zabbix *vmware collector*（vmware 采集器）进程完成对虚拟机的数据采集 - 这些进程通过SOAP协议收集包括必要的VMware web服务信息，对这些信息进行预处理并且存储于Zabbix Server的共享内存。2. Zabbix *poller* （轮询）进程通过[VMware monitoring item keys](/manual/vm_monitoring/vmware_keys)完成对数据的检索。Zabbix将采集的数据分为两种，分别是VMware 配置数据和VMware性能计算数据。这两种类型的数据都由*vmware collector*独自完成采集。下列所统计的参数都是可查看的VMware 性能计算信息：- Datastore（数据存储）- Disk device（磁盘设备）- CPU- Power（电源）- Network interface（网络接口）- Custom performance counter items（自定义性能计算参数）用户若对完整的VMware 性能计算参数有查阅需求，请查看[*VMware monitoring item keys*](/manual/vm_monitoring/vmware_keys#footnotes)。请注意，Vmware事项的检索频率依赖于[vmware.eventlog](/manual/vm_monitoring/vmware_keys#vmware.eventlog)的轮询间隔，且该间隔不能小于5秒钟。</target> </trans-unit> <trans-unit id="68c3f7d5" xml:space="preserve"> <source>#### ConfigurationIf Zabbix server is compiled from [sources](/manual/installation/install#configure_the_sources), it must be compiled with the `--with-libcurl --with-libxml2` configuration options to enable virtual machine monitoring.Zabbix packages are compiled with these options already enabled.The following Zabbix server configuration file parameters can be modified for virtual machine monitoring:- [`StartVMwareCollectors`](/manual/appendix/config/zabbix_server#startvmwarecollectors)::: noteclassicIt is recommended to enable more collectors than the number of monitored VMware services;otherwise, the retrieval of VMware performance counter statistics might be delayed by the retrieval of VMware configuration data (which takes a while for large installations).<br><br>Generally, the value of `StartVMwareCollectors` should not dip below `2` and should not exceed twice the amount of monitored VMware services: Amount of services < `StartVMwareCollectors` < (Amount of services \* 2).For example, when monitoring one VMware service, set `StartVMwareCollectors` to `2`; when monitoring three services, set `StartVMwareCollectors` to `5`.<br><br>Note that the required number of collectors also depends on the scope of the VMware environment, and the `VMwareFrequency` and `VMwarePerfFrequency` configuration parameters.:::