[BUG]: Concurrent monitoring: CPU data deletion mistiming can lead to no results.

[GitTorre]

Bug Details

Scope

This issue applies to AppObserver, and only when AppObserverEnableConcurrentMonitoring is enabled, and you are monitoring several services (which is the only reason you would enable concurrent monitoring on capable hardware).

Problem

Random occurrences of FabricResourceUsageData.Data containers not containing any items for CPU data. This is not consistent or frequent but can take place due to a data clearing bug in ObserverBase.ProcessResourceDataReportHealth.

Solution

Until 3.2.6 ships, if you experience this often, disable AppObserverEnableConcurrentMonitoring configuration in ApplicationManifest.xml.

The easiest solution for you for now, if you build the code yourself, is to replace the data.ClearData() call at the end of the ObserverBase.ProcessResourceDataReportHealth function with

if (ObserverName != ObserverConstants.AppObserverName) 
{
     data.ClearData();
}

[GitTorre]

Fix is in develop branch.

[GitTorre]

Fix Shipped in 3.2.6.