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
Is your feature request related to a problem?
When using a SelectConnection adapter, the "receive" spans are not generated, and the trace context is not propagated from message header (even if traceparent header is there)
Describe the solution you'd like
When autoinstrumenting pika, the tracing behavior would be the same when you use BlockingConnection or SelectConnection
Describe alternatives you've considered
For now we are going to propagate the context "by hand", similarly as what is described in this stackoverflow answer
It also works the other way round. When you are publishing using select connection, the traces are not propagated into the message (the header is not there).
Activity
CucumisSativus commentedon Jul 5, 2022
It also works the other way round. When you are publishing using select connection, the traces are not propagated into the message (the header is not there).