OpenTelemetry pipeline behaviors for metrics/tracing/logging

[martinothamar]

I think it could be useful to have a package called Mediator.OpenTelemetry or OpenTelemetry.Instrumentation.Mediator or something like that which would contain a pipeline behavior that would instrument all messages flowing through Mediator, similarly to how OpenTelemetry.Instrumentation.AspNetCore instruments all HTTP requests

[zidad]

hi @martinothamar, is something like this package already available?

[martinothamar]

Not yet unfortunately, in projects I've often implemented a behavior with traces and metrics as needed. I think what makes sense these days is to built it into Mediator directly and not as a secondary package

[zidad]

I think that makes total sense indeed :)

[Neo-vortex]

We’ve been using this internally on our team for a while, and today I published it publicly: Neovortex.Mediator.OpenTelemetry
.

If you’re interested, we could collaborate to bring it into the Mediator ecosystem—either as a separate package under the Mediator namespace or integrated internally ( we can also consider any change that team wants) .

One important consideration is that most people probably wouldn’t want to pull in the full OpenTelemetry dependencies just for a small project. It would make sense to keep it under the Mediator namespace, but as a separate package altogether.

[martinothamar]

Cool! I was hoping to avoid all of the OTel packages and just rely on System.Diagnostics stuff (leaving SDK/export config to the user, just exposing the ActivitySource and Meter names). Will take a look when I get around to continuing this work, hopefully this month