%3CLINGO-SUB%20id%3D%22lingo-sub-1846074%22%20slang%3D%22en-US%22%3EExperiencing%20data%20error%20for%202%20network%20metrics%20in%20VM%20Insights%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1846074%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%3E%0A%3CP%3EUpdate%3A%20We%20have%20released%20a%20hotfix%20for%20this%20issue%20in%20all%20the%20regions%20on%2011%2F16.%20The%20data%20for%20network%20metrics%20(Network%20ReadBytesPerSecond%2C%20Network%20WriteBytesPerSecond)%20are%20correctly%20recorded%20in%20the%20InsightsMetrics%20table%20in%20Logs.%20The%20data%20also%20reflects%20on%20Bytes%20Sent%20Rate%20and%20Bytes%20Received%20Rate%20charts%20under%20the%20Performance%20tab.%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E_____________________________________________________________________________________________%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EChanges%20deployed%20starting%20on%20October%2024th%2C%202020%20for%20Azure%20Monitor%20for%20Virtual%20Machines%20resulted%20in%20sending%20values%20of%200%20for%20the%20network%20metrics%20(Network%20ReadBytesPerSecond%2C%20Network%20WriteBytesPerSecond)%20to%20the%20InsightsMetrics%20table%20in%20Logs.%20The%20correct%20data%20is%20not%20rendered%20on%20the%20Bytes%20Sent%20Rate%20and%20Bytes%20Received%20Rate%20charts%20under%20the%20Performance%20tab.%20The%20issue%20only%20affects%20Windows%20VMs%20that%20have%20VM%20Insights%20enabled.%20Linux%20VMs%20with%20VM%20Insights%20work%20as%20expected.%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3ERoot%20cause%3A%20The%20VM%20Insights%20Windows%20Management%20Pack%20version%208.0.1.781%20has%20a%20bug%20which%20results%20in%20sending%200%20for%20the%20network%20metrics%20to%20the%20InsightsMetrics%20table.%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EIncident%20Timeline%3A%20October%2024%2C%202020%2C%20to%20present%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EUntil%20we%20resolve%20this%20issue%2C%20you%20can%20monitor%20the%20network%20metrics%20by%20running%20a%20log%20query%20on%20the%20VMConnection%20table%20for%20Bytes%20sent%20and%20received%20trends.%20Please%20refer%20to%20the%20example%20log%20query%20here%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fazure-monitor%2Finsights%2Fvminsights-log-search%23bytes-sent-and-received-trends%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fazure-monitor%2Finsights%2Fvminsights-log-search%23bytes-sent-and-received-trends%3C%2FA%3E)%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EWe%20are%20working%20hard%20to%20roll%20out%20a%20fix%20as%20soon%20as%20possible.%20We%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20VM%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E-%20Jack%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1846074%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Update: We have released a hotfix for this issue in all the regions on 11/16. The data for network metrics (Network ReadBytesPerSecond, Network WriteBytesPerSecond) are correctly recorded in the InsightsMetrics table in Logs. The data also reflects on Bytes Sent Rate and Bytes Received Rate charts under the Performance tab.

 
_____________________________________________________________________________________________
 
Changes deployed starting on October 24th, 2020 for Azure Monitor for Virtual Machines resulted in sending values of 0 for the network metrics (Network ReadBytesPerSecond, Network WriteBytesPerSecond) to the InsightsMetrics table in Logs. The correct data is not rendered on the Bytes Sent Rate and Bytes Received Rate charts under the Performance tab. The issue only affects Windows VMs that have VM Insights enabled. Linux VMs with VM Insights work as expected.
 
Root cause: The VM Insights Windows Management Pack version 8.0.1.781 has a bug which results in sending 0 for the network metrics to the InsightsMetrics table.
  
Incident Timeline: October 24, 2020, to present
 
Until we resolve this issue, you can monitor the network metrics by running a log query on the VMConnection table for Bytes sent and received trends. Please refer to the example log query here (https://docs.microsoft.com/azure/azure-monitor/insights/vminsights-log-search#bytes-sent-and-receive...)
 
We are working hard to roll out a fix as soon as possible. We understand that customers rely on Azure Monitor VM Insights as a critical service and apologize for any impact this incident caused.
 
- Jack