Details
-
Incident report
-
Resolution: Commercial support required
-
Trivial
-
None
-
5.0.26
-
Ubuntu 20.04.41
vSphere/vCenter 7.0.3.00700 and 6.5.0.40000
Description
Steps to reproduce:
- Add vCenter host to zabbix via built-in template
- Start monitoring huge production
- See hundred of logs/unsupported items per day
Result:
1671:20220726:125532.755 item "[id-id-id-id]:vmware.vm.vfs.dev.read[\{$VMWARE.URL},\{HOST.HOST},scsi0:11,ops]" became not supported: Timeout was reached
1674:20220726:125517.722 item "dc-vcenter:vmware.datastore.read[\{$VMWARE.URL},DS-01,latency]" became not supported: Counter datastore/totalReadLatency[average] for datastore DS-01 is not available for hypervisor hypervisor.corp: timeout was reached
(many times, many items)
Expected:
no timeouts or unsupported items
Problem occurred on 2 different environments virtual and physical zabbix server and different vcenter version. To reproduce problem you need to monitor ~2000 items, update interval is 1 minute.
It occurs periodically, and restored too:
1671:20220726:134932.535 item "id-id-id-id:vmware.vm.cpu.ready[\{$VMWARE.URL},\{HOST.HOST}]" became supported
cat /var/log/zabbix/zabbix_server.log | grep vmware | grep -c 'became supported'
118938
config:
- Option: StartVMwareCollectors
- Number of pre-forked vmware collector instances.
#- Mandatory: no
- Range: 0-250
- Default:
StartVMwareCollectors=8
- Option: VMwareFrequency
- How often Zabbix will connect to VMware service to obtain a new data.
#- Mandatory: no
- Range: 10-86400
- Default:
VMwareFrequency=60
- Option: VMwarePerfFrequency
- How often Zabbix will connect to VMware service to obtain performance data.
#- Mandatory: no
- Range: 10-86400
- Default:
VMwarePerfFrequency=60
- Option: VMwareCacheSize
- Size of VMware cache, in bytes.
- Shared memory size for storing VMware data.
- Only used if VMware collectors are started.
#- Mandatory: no
- Range: 256K-2G
- Default:
VMwareCacheSize=32M
- Option: VMwareTimeout
- Specifies how many seconds vmware collector waits for response from VMware service.
#- Mandatory: no
- Range: 1-300
- Default:
VMwareTimeout=300