Replies: 1 comment 3 replies
-
@edtshuma you may be missing the fact that this client does not support OpenTelemetry. #1261 was not finished and to my knowledge, there were no alternatives merged. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I have a .Net Class Library project which implements RabbitMQ producers and consumers. I have added OpenTelemetry/Jaeger trace context to the message headers but at runtime when I inspect the message's Headers property it is null.
The tracing context is being generated correctly but it seems the trace context, tags as well as baggage are all not being added to the headers.
Reproduction steps
This is the publisher code (truncated for brevity) :
The trace context is being picked up successfully:
but the even after stepping through , either of the context or tags, is available in the headers:
Expected behavior
The trace context , tags and baggage should be added in
props.Headers
and they should be available for retrieval at the consumer end. As of now these properties are not being sent over the wireAdditional context
As a test I added the SpanId and TraceId explicitly as a pair of custom headers as below:
The properties are available in the message BasicProperties header but they are not available at the consumer end:
At the consumer end I am retrieving the headers via
BasicDeliverEventArgs ea
but strangely enough the headers are null :Implementing this based on --> here
What am I missing?
Beta Was this translation helpful? Give feedback.
All reactions