Tips to troubleshoot why data collection in vRealize Operations Manager appears slow

Products

• VMware Aria Suite

Issue/Introduction

If the vRealize Operations Manager data analytics process does not match the speed of incoming data, or the data collection process stops, data collected in the last collection cycle displays slowly or not at all.

Resolution

What appears to be erratic or halted data collection can be due to problems with either the analytics or collector process running on a vRealize Operations Manager node. To troubleshoot issues related to these processes, log in to the vCenter Server and perform the following checks related to the infrastructure of your environment.

• Check the read/write latency for the Datastore objects that are connected to vRealize Operations Manager VMs and ensure that values are under 10 milliseconds on average. Higher latency times might slow the data processing or storage rate and cause data collection to become erratic. To address this problem, consider moving to faster storage.
  
• Check the CPU and memory usage commitment for the hosts on which vRealize Operations Manager VMs are deployed. If the the CPU or memory usage on any host is over-committed, verify that CPU ready, memory ballooning metrics are acceptable. To accommodate the CPU usage pattern of vRealize Operations Manager, the ideal ratio of host CPU to virtual CPU is one to one.
• Verify that disks for the vRealize Operations Manager VMs do not contain any snapshots. Unneeded snapshots can affect I/O performance and result in slower data processing or storage rates.
• Verify that the load average that is displayed from the top command does not exceed the number of CPUs allocated for the vRealize Operations Manager VM. A higher load average number indicates high CPU contention.
• To verify that the there are no network issues, check the metrics for packets dropped by the vRealize Operations Manager VMs.

Always verify that your vRealize Operations Manager configuration conforms to the sizing guidelines in KB 2093783.

If you do not discover why data collection has stopped after performing all checks, contact VMware support.