Source of vm_monitoring.xliff - documentation

<?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="nb-NO" datatype="plaintext" original="manual/vm_monitoring.md">

    <body>

      <trans-unit id="3ca85094" xml:space="preserve">

        <source># 10 Virtual machine monitoring</source>

      </trans-unit>

      <trans-unit id="621e23e6" xml:space="preserve">

        <source>#### Overview

Zabbix 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">#### Overview

Zabbix 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 templates for monitoring VMware vCenter or ESXi hypervisors.

The minimum required VMware vCenter or vSphere version is 5.1.</target>

      </trans-unit>

      <trans-unit id="4c2e8939" xml:space="preserve">

        <source>#### Data collection

Virtual 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 items

For 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>

      </trans-unit>

      <trans-unit id="68c3f7d5" xml:space="preserve">

        <source>#### Configuration

If 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)

::: noteclassic

It 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).