On Sylsload VMWare Agents, some VMWare latency counters generate errors in the _sldvmhost_worker.log / _sldvmcluster_worker.log when being collected as an abnormally high value is retrieved.
Example of the error in the logs:
_sldvmcluster_worker - WARNING - Consolidated data will not be historized because value exceeds limit (number is too big). [Perf-VirtualMachine_datastore.maxTotalLatency.latest_S - CGa#HUX162-PMSI-Pilot#0512181010#68321272869683200] Impacted metric : CGa => « Perf-VirtualMachine_datastore.maxTotalLatency.latest_S » Workaround : Comments the line in the files "sldvmcluster.cnv" & " _sldvmcluster_worker.cnv" #Perf-VirtualMachine_datastore.maxTotalLatency.latest_S | CGa# | 100 | 1.0000000000000000 | 3 | - | VM Specific(x) - highest datastore latency
Abnormally high latency values cannot be written / used and generate errors in the product log.
Release : 6.0x
Component/s : Sysload Agent VMWare (Cluster and Host)
Remove the impacted line in the files "sldvmcluster.cnv" & " _sldvmcluster_worker.cnv", example:
Perf-VirtualMachine_datastore.maxTotalLatency.latest_S | CGa# | 100 | 1.0000000000000000 | 3 | - | VM Specific - highest datastore latency
Update to a fix version listed below or a newer version if available.
Fix version(s):
Component: Sysload Agent VMWare Cluster and Sysload Agent VMWare Host
Agent VMWare Cluster/Host 6.01HF2 - Scheduled 15th January 2021