machine monitoring. It allows to monitor VMware vCenter and vSphere installations for various VMware hypervisor and virtual machine properties and statistics. Zabbix can use low-level discovery rules to automatically configuration. • vmware.vm.perfcounter and vmware.hv.perfcounter items were added to allow custom hypervisor and virtual machine performance counter monitoring. A configurable timeout was added to VMware 3.1 VMware monitoring A new vmware.hv.sensor.health.state key has been added to monitor VMware hypervisor health state rollup sensor. The vmware.hv.status key, which was changed in Zabbix 2.2.10 to use

VMware Hypervisor host, check that the event log item vmware.eventlog[,,] is present and working properly. Note that the event log item could already be present on the hypervisor if the the Template VM VMware template has been linked during the host creation. 2. On the VMware Hypervisor host, create a dependent item of ’Log’ type and set the event log item as its master. In the ”Preprocessing” used for discovered entities and, typically, should not be manually linked to a host: • VMware Hypervisor • VMware Guest 502 Host macros configuration To use VMware simple checks, the host must have

working VMware Hypervisor host check that the event log item vmware.eventlog[,] is present and working properly. Note that the event log item could already be present on the hypervisor if the Template Template VM VMware template has been linked during the host creation. 2. On the VMware Hypervisor host create a dependent item of ’Log’ type and set the event log item as its master. In the ”Preprocessing” used for discovered entities and, typically, should not be manually linked to a host: • VMware Hypervisor • VMware Guest 505 Host macros configuration To use VMware simple checks, the host must have

configuration. • vmware.vm.perfcounter and vmware.hv.perfcounter items were added to allow custom hypervisor and virtual machine performance counter monitoring. 24 A configurable timeout was added to VMware device discovery transfer rate item prototype names were fixed for Template Virt VMware Guest. The hypervisor network interface, virtual machine network interface and virtual machine disk device transfer name[,] VMware hypervisor cluster name. String url - VMware service URL uuid - VMware hypervisor host name vmware.hv.cpu.usage[,] VMware hypervisor processor usage (Hz).

has been added to monitor VMware hypervisor health state rollup sensor. The vmware.hv.status key was reverted back to its original implementation and now uses the hypervisor overall status property. A new {#DATASTORE},pfree] to monitor VMware datastore capacity were added to template Template Virt VMware Hypervisor datastore discovery. Template changes in 3.0.7 The vmware.vm.cpu.ready item unit and description name[,] VMware hypervisor cluster name. String url - VMware service URL uuid - VMware hypervisor host name vmware.hv.cpu.usage[,] VMware hypervisor processor usage (Hz).

rp.memory[]. The items vmware.hv.network.in[] and vmware.hv.network.out[], used for monitoring hypervisor network traffic, now support additional NIC counters. Four new mode options have been added to fields, including user- defined custom attribute values. The items vmware.hv.discovery[], used for hypervisor discovery, and vmware.cluster.discovery[], used for clusters discovery, now return information working VMWare Hypervisor host check that the event log item vmware.eventlog[,] is present and working properly. Note that the event log item could already be present on the hypervisor if the Template

functionality would not work for these items. Item changes * ''vmware.hv.discovery'' item for VMware hypervisor discovery now returns two [[:manual/vm_monitoring/discovery_fields|additional fields]]: {#PARENT {#PARENT.NAME} and {#PARENT.TYPE}, returning name and type of the container that stores the hypervisor respectively See also • Template changes 33 9 What’s new in Zabbix 4.0.4 Items A new regex_excl_dir been moved from hypervisor level to vCenter level. As a result datastores are discovered and datastore info is collected only once for each datastore instead of one time per each hypervisor. 37 Within

name[,] VMware hypervisor cluster name. String url - VMware service URL uuid - VMware hypervisor host name vmware.hv.cpu.usage[,] VMware hypervisor processor usage (Hz). URL uuid - VMware hypervisor host name vmware.hv.datacenter.name[,] VMware hypervisor datacenter name. String url - VMware service URL uuid - VMware hypervisor host name vmware datastore.discovery[,] Discovery of VMware hypervisor datastores. JSON object url - VMware service URL uuid - VMware hypervisor host name vmware.hv.datastore.read[,,

been moved from hypervisor level to vCenter level. As a result datastores are discovered and datastore info is collected only once for each datastore instead of one time per each hypervisor. Within this name[,] VMware hypervisor cluster name. String url - VMware service URL uuid - VMware hypervisor host name vmware.hv.cpu.usage[,] VMware hypervisor processor usage (Hz). URL uuid - VMware hypervisor host name vmware.hv.datacenter.name[,] VMware hypervisor datacenter name. String url - VMware service URL uuid - VMware hypervisor host name vmware