Skip to content

Is there plans to have pika SelectConnection adapter to be autoinstrumented ? #920

@TonyRoussel

Description

@TonyRoussel

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

Activity

CucumisSativus

CucumisSativus commented on Jul 5, 2022

@CucumisSativus

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @owais@CucumisSativus@TonyRoussel

      Issue actions

        Is there plans to have pika SelectConnection adapter to be autoinstrumented ? · Issue #920 · open-telemetry/opentelemetry-python-contrib