Skip to content

FabricObserver 3.2.14
Compare
Choose a tag to compare
@GitTorre GitTorre released this 31 Jan 19:36
86700705
4b9e786
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

FabricObserver 3.2.14, ClusterObserver 2.2.8 SFPkgs with Microsoft-signed binaries. Microsoft-signed Nupkgs will be located in the nuget.org gallery.

Deploy to Azure

FabricObserver Changes

  • Breaking Change: Telemetry configuration settings are now required to be overridden in ApplicationManifest.xml to support versionless, parameter-only application upgrades for telemetry settings. See Issue 292 for details. Just move your related settings' Value strings from Settings.xml to ApplicationManifest.xml app parameter (the names of these settings are the same).
  • Bug fixes and performance improvements to address AppObserver (in concurrency mode) consuming high CPU if misconfigured. There are now throttles and guardrails in place that will override any related user configuration that is deemed "dangerous" with respect to CPU consumption.
  • Bug fix in app param update for log path and max archive lifetime settings.
  • Updated nuget package dependencies to latest versions.

ClusterObserver Changes

  • Breaking Change: Telemetry configuration settings are now required to be overridden in ApplicationManifest.xml to support versionless, parameter-only application upgrades for telemetry settings. See Issue 292 for details. Just move your related settings' Value strings from Settings.xml to ApplicationManifest.xml app parameter (the names of these settings are the same).
  • Bug fix in app param update for log path and max archive lifetime settings.
  • Updated nuget package dependencies to latest versions.

Note: Microsoft.ServiceFabricApps.FabricObserver.Extensibility.3.2.14 shipped with an incorrect dependency specification. The issue is that it will build using the wrong version of DependencyInjection.Abstractions (7.0.0), which will break the build of your plugin. There are two simple fixes:

1.) Don't build your plugins targeting this release of Extensibility package. That is fine, generally, in fact. There is nothing in this release that would prevent your plugins from building and then from working when hosted in FO/CO 3.2.14 process. There are seldom breaking changes in ObserverBase and related code that break plugin building from release to release of the package. When your plugin is hosted in FO or CO, the version of these services will already have the same version of Extensibility library in place in their code packages. This means that your plugin will target that version at runtime.

2.) Add a Package Reference in your plugin csproj files that reference the correct version of DependencyInjection.Abstractions:

<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="8.0.0" />

Again, option 2 is not necessary as there are no changes that will impact the behavior of your existing plugin(s) in this release of Extensibility package and the primary goal of using this package is to build your plugins without having to consume the entire FO/CO nuget package and then having to keep track of dependency versions of DependencyInjection.Abstractions when these are updated to later versions in the Extensibility project.

Assets 10
Loading