-
Type:
Problem report
-
Resolution: Fixed
-
Priority:
Major
-
Affects Version/s: 4.0.0beta2, 4.0.1rc1
-
Component/s: Proxy (P), Server (S)
-
Sprint 46, Nov 2018
-
0.125
Steps to reproduce:
- Set config.vpxd.stats.maxQueryMetrics to -1 as https://kb.vmware.com/s/article/2107096Â suggest in solution step 7.
- Discover of VSphere
Result:
zabbix_server.log shows:
error reason for "VSpherehost:vmware.cluster.discovery[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.hv.discovery[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.vm.discovery[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.eventlog[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.fullname[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.version[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
Expected:
We should be able to collect VMWare when the limit on query size is disabled or unlimited.
It should also collect when the limit is not specified (config.vpxd.stats.maxQueryMetrics not set)
- caused by
-
ZBX-14853 config.vpxd.stats.maxQueryMetrics
-
- Closed
-