MQ Boundaries are not crossed, Redis call and MQ consumer not auto instrumented

[mnadeem]

Describe the bug

Three things

1. MQ (Rabbit MQ) calls are not crossing the component boundary as as in rest calls (Trace Ids are getting changed)

2. Redis calls are not instrumented

3. RabbitMQ Consumer is not auto instrumented, I had to use @WithSpan

Steps to reproduce

https://github.com/mnadeem/boot-opentelemetry-tempo ==> look for complex branches, same behavior is across the branches.

mvn clean package docker:build

and then

docker-compose up

What did you expect to see?
A clear and concise description of what you expected to see.

What did you see instead?
A clear and concise description of what you saw instead.

What version are you using?
(e.g., v0.9.0, 393e4a2, etc) : 0.15.0, 0.16.0 and 0.17.0

Environment
Compiler: (e.g., "AdoptOpenJDK 11.0.6") : Oracle jdk 8
OS: (e.g., "Ubuntu 20.04") : Widows 10
Runtime (if different from JDK above): (e.g., "Oracle JRE 8u251")
OS (if different from OS compiled on): OS is same as that of compiled one, Widows 10

Additional context
Add any other context about the problem here.

[mnadeem]

Note: Redis is instrumented with Lettuce 5 and not with 6

[mnadeem]

For rabbitMQ consumer I doing the following way as a work around for the time being

https://github.com/mnadeem/boot-opentelemetry-tempo/blob/0.15.0_complex/boot-otel-tempo-mq-consumer/src/main/java/io/opentelemetry/example/flight/messaging/FlightMQConsumer.java#L38

[mnadeem]

I see that, RabbitMQ Client , 2.7+ is supported

And I am using 5.9

From RabbitMQ producer everything is okay, span created, parent tracer passed.

Consumer receiving it as well.

However at the consumer side, parent context is not considered and new span is not created.

[mateuszrzeszutek]

Hi @mnadeem ,
Can you create a separate enhancement issue for implementing Lettuce 6 instrumentation?

[mnadeem]

@mateuszrzeszutek

In this ticket we are talking about rabbitmq and not redis

not sure if I am missing anything

[mateuszrzeszutek]

Oh, you mentioned that "Redis calls are not instrumented" so I thought that you wanted to have Lettuce 6 instrumented as well

[mnadeem]

Apologies, missed it

[mnadeem]

Created a separate enhancement request for Lettuce,

What needs to be done for RabbitMQ ?

[mateuszrzeszutek]

Thanks!
It needs to be fixed -- this most certainly looks like a bug. Whatever spring uses for @RabbitListerer-annotated methods is probably not instrumented.