Zabbix 4.0 not retrieving VMWare Data
Zabbix: 4.0.1
vCenter : 6.5.0
vSphere Hosts: 55
Total VMs: 3131
I've re-deployed a Zabbix instance to monitor our VMWare environment but letting it run for 24 hours have yet to see any hosts / vms / etc added to the system via the discovery rules. I am seeing this in the logs though:
66179:20181114:172042.574 item "MY_VCENTER_SERVER:vmware.vm.uptime[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172057.601 item "MY_VCENTER_SERVER:vmware.hv.cpu.usage[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172058.605 item "MY_VCENTER_SERVER:vmware.hv.datacenter.name[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172108.627 item "MY_VCENTER_SERVER:vmware.hv.memory.size.ballo oned[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172109.632 item "MY_VCENTER_SERVER:vmware.hv.memory.used[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172110.634 item "MY_VCENTER_SERVER:vmware.hv.network.in[{$URL},{HOST.HOST},bps]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172111.637 item "MY_VCENTER_SERVER:vmware.hv.network.out[{$URL},{HOST.HOST},bps]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172112.640 item "MY_VCENTER_SERVER:vmware.hv.sensor.health.sta te[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172113.644 item "MY_VCENTER_SERVER:vmware.hv.status[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
I've checked the forums and the fix (which worked with a lost 3.2 deployment) was to apply the config changes in https://kb.vmware.com/s/article/2107096 which has already been done. The log lines above may be a false flag as I had linked all of the VMWare templates to the vCenter entry instead of the top level.
vCenter : 6.5.0
vSphere Hosts: 55
Total VMs: 3131
I've re-deployed a Zabbix instance to monitor our VMWare environment but letting it run for 24 hours have yet to see any hosts / vms / etc added to the system via the discovery rules. I am seeing this in the logs though:
66179:20181114:172042.574 item "MY_VCENTER_SERVER:vmware.vm.uptime[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172057.601 item "MY_VCENTER_SERVER:vmware.hv.cpu.usage[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172058.605 item "MY_VCENTER_SERVER:vmware.hv.datacenter.name[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172108.627 item "MY_VCENTER_SERVER:vmware.hv.memory.size.ballo oned[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172109.632 item "MY_VCENTER_SERVER:vmware.hv.memory.used[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172110.634 item "MY_VCENTER_SERVER:vmware.hv.network.in[{$URL},{HOST.HOST},bps]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172111.637 item "MY_VCENTER_SERVER:vmware.hv.network.out[{$URL},{HOST.HOST},bps]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172112.640 item "MY_VCENTER_SERVER:vmware.hv.sensor.health.sta te[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
66179:20181114:172113.644 item "MY_VCENTER_SERVER:vmware.hv.status[{$URL},{HOST.HOST}]" became not supported: Cannot convert maxQueryMetrics from -1.
I've checked the forums and the fix (which worked with a lost 3.2 deployment) was to apply the config changes in https://kb.vmware.com/s/article/2107096 which has already been done. The log lines above may be a false flag as I had linked all of the VMWare templates to the vCenter entry instead of the top level.
Comment