Zabbix can use a low-level discovery rule to automatically discover VMware hypervisors and virtual machines.Īll mandatory input fields are marked with a red asterisk.ĭiscovery rule key in the above screenshot is vmware.hv. See also the VMware knowledge base article. To support datastore capacity metrics Zabbix requires VMware configuration parameter to be at least 64. Also keep in mind that this value also depends on your VMware environment size and VMwareFrequency and VMwarePerfFrequency configuration parameters (see below).įor more details, see the configuration file pages for Zabbix server and proxy. Note that in most cases this value should not be less than 2 and should not be 2 times greater than the number of VMware services that you monitor. if you have 1 VMware service to monitor set StartVMwareCollectors to 2, if you have 3 VMware services, set it to 5.
![internet usage monitor virtual appliance internet usage monitor virtual appliance](https://cdn3.geckoandfly.com/wp-content/uploads/2015/09/connectify-hotspot.jpg)
Where servicenum is the number of VMware services. Servicenum < StartVMwareCollectors < (servicenum * 2) This value depends on the number of VMware services you are going to monitor.
![internet usage monitor virtual appliance internet usage monitor virtual appliance](https://cdn3.geckoandfly.com/wp-content/uploads/2015/11/du-meter.jpg)
The following configuration file options can be used to tune the Virtual machine monitoring: Configurationįor virtual machine monitoring to work, Zabbix should be compiled with the -with-libxml2 and -with-libcurl compilation options. Otherwise retrieval of VMware performance counter statistics might be delayed by the retrieval of VMware configuration data (which takes a while for large installations).Ĭurrently only datastore, network interface and disk device statistics and custom performance counter items are based on the VMware performance counter information. Because of this it is recommended to enable more collectors than the monitored VMware services. Both types are collected independently by vmware collectors. Virtual appliances are great for the same reasons physical appliances took the IT world by storm: They make deployment a snap - even instantaneous - while at the same time reducing costs. Starting with Zabbix version 2.4.4 the collected data is divided into 2 types: VMware configuration data and VMware performance counter data. Then, this data is retrieved by pollers using Zabbix simple check VMware keys. Those processes obtain necessary information from VMware web services over the SOAP protocol, pre-process it and store into Zabbix server shared memory.
![internet usage monitor virtual appliance internet usage monitor virtual appliance](https://archinect.imgix.net/uploads/28/28d4e186c9d649e3425d36b0e5aec3f1.jpg)
First, virtual machine data is gathered by vmware collector Zabbix processes. The virtual machine monitoring is done in two steps. The minimum required VMware vCenter or vSphere version is 4.1. The default dataset in Zabbix offers several ready-to-use templates for monitoring VMware vCenter or ESX hypervisor. Zabbix 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. Support of monitoring VMware environments is available in Zabbix starting with version 2.2.0.