You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this library is a nice, simplified wrapper arround the official amqp library, it would make sense to also support observability using OpenTelemetry out of the box (of course, it would be optional).
I have already implemented this in my own personal development library, but It would make sense to also include it here. I would like to know your thoughts if this is a possibility and how we could approach this idea/implementation.
The text was updated successfully, but these errors were encountered:
As mentioned here, I do not think this will be done using otel packages. It is very easy to instrument your publish/consume using a custom wrapper (i.e. injecting and retrieving trace/span ids in amqp message headers)
As mentioned here, I do not think this will be done using otel packages. It is very easy to instrument your publish/consume using a custom wrapper (i.e. injecting and retrieving trace/span ids in amqp message headers)
I am aware that the goal is to keep dependencies to a minimum and that instrumenting is easy. Im just pointing out that it would be nice to do so in a simplified/standardized way, so it works out of the box.
Hey!
Since this library is a nice, simplified wrapper arround the official amqp library, it would make sense to also support observability using OpenTelemetry out of the box (of course, it would be optional).
I have already implemented this in my own personal development library, but It would make sense to also include it here. I would like to know your thoughts if this is a possibility and how we could approach this idea/implementation.
The text was updated successfully, but these errors were encountered: