Skip to content

FabricObserver 3.2.4.960
Compare
Choose a tag to compare
@GitTorre GitTorre released this 08 Dec 17:30
65633122
084740a

FabricObserver 3.2.4.960 - SFPkgs with Microsoft-signed binaries. Microsoft-signed Nupkgs will be located in the nuget.org gallery.

NOTE: This release requires SF Runtime versions 9.0 and higher and targets .NET 6.

FabricObserver Changes

  • Modifications to how AppObserver monitors RG memory limits for service processes (and their children): If you specify both MemoryInMB and MemoryInMBLimit, FO will always choose the absolute value specified in the MemoryInMBLimit setting for the code package. This feature enables you to have FO alert you when one of your services is approaching (d)OOM (Windows-only today. Linux support is coming). You can configure when FO should warn you (80% of the way there? 90%? Whatever makes your heart sing).

  • Modifications to how AppObserver detects and monitors Guest Executable services and service helper code packages.

  • Protection against over-calling netstat for TCP port monitoring. Windows does not offer a publicly documented API for getting BOUND state connection info (it’s simple to do, but not in a sanctioned way, therefore not in a Microsoft-owned public Github repo…). As such, FO must rely on making external calls to netstat (via createprocess), which can be relatively expensive both internally (what netstat does…) and externally (Windows Defender stalking FO == CPU abuse). That said, FO employs port data caching and does not abuse netstat.

  • Bug fix: Guest Executable service data contains the usual information - Service name, partition id, replica id, etc.

  • Bug fix: Service helper code package data contains related information about the primary service to which it belongs - Service name, partition id, replica id, etc. This is so you can easily correlate a helper code package to its "owning" service entity. Partition and replica don't really make sense for a helper code package itself, but they are important pieces of information about the related service instance.

  • Removed support for ApplicationInsights InstrumentationKey usage. Instead, you must use the full Connection String. This is because ApplicationInsights has deprecated support for supplying only an InstrumentationKey for authentication/identification to its service. You will see this change reflected in FO's Settings.xml.

  • Performance improvements.

  • Updated nuget package dependencies to latest versions, where possible. Note: If you build plugins and do not use the FO Extensibility nuget package, you must update your Microsoft.Extensions.DependencyInjection.Abstractions reference to version 7.0.0.

Assets 6
Loading