VMWare ESXi 6.7 and 4.2 Zabbix — how to monitor?

Good day!

Zabbix 4.2 on Ubuntu 18.04
ESXi 6.7

Have read several instructions, including the official from Zabbix.

Got UUID, created a user in ESXi with the rights of the RO.
5e84e76d9fcea264870540.jpeg
5e84e777cb787368473305.jpeg

Created host in Gabicce, macros, prescribed, and used the built-in template
5e84e79601fbf267699835.jpeg
5e84e79d6768e737565801.jpeg
But get this result:
5e84e5010033b318975519.jpeg

cat /var/log/zabbix/zabbix_server.log:
14413:20200401:190725.757 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.cpu.model[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14416:20200401:190726.776 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.cpu.num[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14414:20200401:190727.830 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.cpu.threads[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14415:20200401:190728.831 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.memory[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14413:20200401:190729.838 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.model[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14416:20200401:190730.838 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.uuid[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14413:20200401:190731.893 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.hw.vendor[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14415:20200401:190738.980 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.uptime[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14415:20200401:190739.052 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.version[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14415:20200401:190740.119 item "30303734-3536-5a43-4a32-313131433447:vmware.hv.vm.num[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
 14450:20200401:190741.277 discovery rule "30303734-3536-5a43-4a32-313131433447:vmware.hv.datastore.discovery[{$URL},{HOST.HOST}]" became not supported: Timeout was reached
April 16th 20 at 10:31
1 answer
April 16th 20 at 10:33
and you have ESX is the agent Zabbix?
I think not. I think you or
a) appeal to the hypervisor via SNMP
or
b) more likely - knock him Zabbix server API
===
Supplement after I looked the official Doc
https://www.zabbix.com/documentation/4.2/ru/manual...
Monitoring virtual machines is performed in two steps. First, data about the virtual machines is collected by Zabbix vmware collector processes. These processes receive the necessary information from VMware web services over SOAP Protocol podgotovljajut this information and written in the shared memory of the Zabbix server. Then, the data extracted by pollero using VMware keys simple checks in Zabbix.

All the fun, which is written there on works fine. All settings are done on the host which vmware collectors will go to any ESX have.
StartVMwareCollectors - is 2, and the other parameters from this section is also reduced to the form specified in the manual.
using htop you can see that pollari VMWare running on the zabbix server. - donald.Kessler54 commented on April 16th 20 at 10:36
Anton, on the "native" instructions of the network node is not configured. The hypervisor has no agent and target node in the network there you can't. Instead, you take the one node in the network, which are already working vmware Pollera and it adds macros and templates. - rachel commented on April 16th 20 at 10:39
@rachel,
5e858e1840122862970016.jpeg - donald.Kessler54 commented on April 16th 20 at 10:42

Find more questions by tags VMware ESXiZabbixUbuntu