Tomasz Maruszak

Actually, you can make a generic message interceptor as explained here https://github.com/zarusz/SlimMessageBus/blob/master/docs/intro.md#generic-interceptors You can see this working for the outbox plugin https://github.com/zarusz/SlimMessageBus/blob/master/src/SlimMessageBus.Host.Outbox/Configuration/ServiceCollectionExtensions.cs#L12

The feature should be generating instrumentation using: https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource https://learn.microsoft.com/en-us/dotnet/core/diagnostics/diagnosticsource-diagnosticlistener When the extension is built it needs to follow this: https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/docs/trace/extending-the-sdk/README.md#instrumentation-library

Another useful link https://github.com/prometheus-net/prometheus-net/blob/master/Benchmark.NetCore/SdkComparisonBenchmarks.cs https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/

@socdream and @eByte23 did you integrate successfully with ADFS and this library (over SAML2.0 protocol)? What I can tell the library worked well with PingFederate as identity provider, now wondering...

@EtherZa Sounds like a good use case. If you willing to contribute I am happy to review a PR. Perhaps it's a circuit breaker even.