Vmware Probe fails to read Resource

Document ID : KB000102749
Last Modified Date : 20/06/2018
Show Technical Document Details
Introduction:
The Vmware Probe fails to retreive Performance Metrics and following error message appears in the vmware.log file.

( 1m 12s ) Visitor: Jun 18 09:32:12:221 [Data Collector - ibwvcv01, vmware] PERF: START: Update perf metrics Jun 18 09:32:13:279 [Performance Metric Collection - 12, vmware] Batch fetching of perf metrics failed. Retrying as individual requests Jun 18 09:32:16:049 [Performance Metric Collection - 28, vmware] Batch fetching of perf metrics failed. Retrying as individual requests Jun 18 09:32:16:615 [Performance Metric Collection - 1, vmware] Batch fetching of perf metrics failed. Retrying as individual requests Jun 18 09:33:07:611 [Thread-6, vmware] ExecutorService tasks failed to complete within one minute. Forcing them down.
Question:
What is the exact meaning of the error message and is there a way to configure the probe to avoid this errors ?
Environment:
vmware probe 6.72
Answer:
By default VMware limits the "vpxd.stats.maxQueryMetrics" to 64. This will cause the probe metric
collection to fail if a Resource Pool/vAPP or a cluster has more than 64 VMs or a Datastore has more
than 64 VMs or disks. You will see an error message such as: “Failed to execute single perf query for
entity ……. Follow VMware KB 2107096 to resolve.”
Solution :
Follow the instructions in the VMware Knowledge Base article "Performance charts are empty" #
2107096 (https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2107096), on how to increase the "vpxd.stats.
maxQueryMetrics." Increase the "vpxd.stats.maxQueryMetrics" to more than the maximum number
of VMs that you have in a resource pool, cluster. Similarly, increase the "vpxd.stats.
maxQueryMetrics" to more than the maximum number of VMs/Disks that you have in a Datastore.
 
Additional Information: