Performance statistics gaps during vMotion - VMware vCenter Server
search cancel

Performance statistics gaps during vMotion - VMware vCenter Server

book

Article ID: 388218

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vCenter Server

Issue/Introduction

In the vSphere Client, performance statistics for virtual machines show intermittent gaps or missing data points in the Monitor > Performance > Overview or Last Day charts.



  • Gaps typically last up to 30 minutes.
  • Network performance charts may also show breaks coinciding with migration tasks.
  • Observation of "brief outages" or "lost connectivity" (stun period) coinciding with these gaps, especially for high-traffic SQL servers or sensitive API calls.
  • In vpxd.log, entries may show the start and completion of DRS-recommended vMotion tasks around the time of the gaps:
    info vpxd[#####] [Originator@#### sub=vpxLro opID= CdrsLoadBalancer-#######-########] [VpxLRO] -- BEGIN lro-######### --  -- DrmExecute --
    info vpxd[#####] [Originator@#### sub=drsExec opID=...] Executing DRM recommended vMotion in ... migrating [vim.VirtualMachine:vm-####, VM_NAME] from host-#### to host-####

Environment

  • vCenter 8.x

Cause

vCenter Server schedules statistics collection at 30-minute intervals. When a virtual machine (VM) undergoes a vMotion migration, the following process occurs:

  1. Performance statistics for the VM are cleared from the source ESXi host upon un-registration.
  2. The destination host begins collecting new statistics only after the migration completes.
  3. If a collection cycle occurs during or immediately after the transition, the interim statistics from the source host are already discarded, resulting in a gap in the vCenter performance charts until the next cycle on the destination host completes.

This is expected behavior and a product limitation of the statistics collection architecture during migrations.

Resolution

Verify that the performance data gaps align with vMotion tasks. No functional fix is required as this is by design.

To troubleshoot or manage the frequency of these gaps:

  1. Verify Task Alignment: Review the Tasks console in vCenter to confirm if vMotion or DRS migration tasks occurred during the missing data intervals.
  2. Review DRS Configuration: If migrations are frequent, consider adjusting the DRS Migration Threshold from "Fully Automated" to a more conservative setting to reduce the number of recommended moves.
  3. Database Validation: If gaps occur without vMotion, ensure the ESXi host and vCenter system times are synchronized and verify if there are stale timestamps in the vpx_host_perfinfo table using the steps in "Performance data is currently not available for this entity" viewing the VM performance tab in vCenter Server"

Additional Information