You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
FabricObserver 3.1.18, ClusterObserver 2.1.11 - SFPkgs with Microsoft-signed binaries. Microsoft-signed Nupkgs are located in the nuget.org gallery.
FabricObserver Changes
Concurrent process monitoring on capable CPU configurations (>= 4 logical processors) which greatly improves AppObserver's performance when monitoring several services. FabricSystemObserver and ContainerObserver also support this feature. This feature is per-observer configurable. See ApplicationManifest.xml and the specific observer sections to enable this feature for capable hardware. Note that if you are not running FO on a multi-core machine, then enabling this feature doesn't do anything (the monitoring and reporting loops will run sequentially).
Added Thread count metric for AppObserver and FabricSystemObserver.
ApplicationInsights Telemetry format change: Numeric data will be held in customMeasurements collection. You will need to modify your existing queries, which assume all data is present in customDimensions collection. This is no longer the case. There are two collections that will be available: customDimensions which contains string,string values and customMeasurements which contains string,double values. For example: given EphemeralPorts telemetry data for application fabric:/foo, customDimensions will contain the app name, node name, etc... customMeasurements will contain the metric name (EphemeralPorts) and corresponding value (say, 4200).
