Microsoft.ServiceFabricApps.FabricObserver.Extensibility 3.2.15

FabricObserver Extensibility Library 3.2.15

FabricObserver.Extensibility is a .NET 6 library for building custom observers that extend FabricObserver's capabilities to match your needs. A custom observer is managed just like a built-in observer.

How to implement an observer using FO's extensibility model

1. Create a new .NET core library project. You should target net6.0 in your csproj because that is the target net SDK version that FabricObserver is built for.

2. Install the latest Microsoft.ServiceFabricApps.FabricObserver.Extensibility nupkg from https://www.nuget.org/profiles/ServiceFabricApps into your plugin project.

3. Write an observer plugin!

Steps

• Create a new class file, MyObserver.cs.

  This is the required signature for your plugin's constructor:

    // FO will provide (and manage) both the FabricClient instance and StatelessServiceContext instance during startup.
    public MyObserver(FabricClient fabricClient, StatelessServiceContext context) : base(fabricClient, context)
    {
    }

• Implement ObserverBase's two abstract functions:

    public override Task ObserveAsync()
    {
    }

    public override Task ReportAsync()
    {
    }

• Create a [PluginTypeName]Startup.cs file

    using System.Fabric;
    using FabricObserver;
    using FabricObserver.Observers;
    using Microsoft.Extensions.DependencyInjection;

    [assembly: FabricObserverStartup(typeof(MyObserverStartup))]
    namespace FabricObserver.Observers
    {
        public class MyObserverStartup : IFabricObserverStartup
        {
            public void ConfigureServices(IServiceCollection services, FabricClient fabricClient, StatelessServiceContext context)
            {
                services.AddScoped(typeof(ObserverBase), s => new MyObserver(fabricClient, context));
            }
        }
    }

• Build, put the output dll and ALL of its dependencies, both managed and native (this is very important), into the Config/Data/Plugins folder in FabricObserver/PackageRoot. You can place your plugin dll and all of its dependencies in its own folder under the Plugins directory (useful if you have multiple plugins). Again, ALL plugin dll dependencies (and their dependencies, if any) need to live in the same folder as the plugin dll. Note that if FabricObserver already employs the same version of dependency dll, then you can omit adding the dependency manually.

• Add a new config section for your observer in FabricObserver/PackageRoot/Config/Settings.xml (see example at bottom of that file) Update ApplicationManifest.xml with Parameters if you want to support Versionless Application Parameter-only Upgrades for your plugin.

• Ship it! (Well, test it first =)