-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Micrometer tracing] PubSub Binder does not propagate tracing data #1995
Comments
We have experimental support for Pub/Sub tracing. Did you try enabling it via |
Hi, my tracing propagation from producer to consumer is working but having issues propagating tracing context to executor threads. Using examples from https://amithkumarg.medium.com/micrometer-tracing-in-spring-boot-context-propagation-for-async-scheduled-newspan-b80f4f4b2c9f It's working on the first message received from the consumer.
But subsequence messages received by the same consumer have
|
@meltsufin thanks for response. Enabling the flag worked. Still 2 remarks from my side:
|
@poznachowski Thanks for the update! I'm glad it worked for you! |
Hello.
We are migrating our SB 2.x services to SB 3.x and it looks like last thing that blocks us is the tracing capability.
We are using Pub/Sub messaging with Spring Cloud Stream abstraction.
I came up with simple project that reproduces the issue: https://github.com/poznachowski/sb3streamtracingpubsub
To reproduce just spin Pub/Sub emulator with docker-compose, run the application and trigger sending / receiving msg with localhost:8080 url.
As can be seen in the logs traceId differs.
There is a lot of layers that are involved and I'm struggling with finding the issue. I dediced to raise the issue here (as opposed to spring cloud stream repository) as I changed the example to use RabbitMQ binder (https://github.com/poznachowski/sb3streamtracingpubsub/tree/rabbit_check) and it works like a charm:
What I've seen is that RabbitTemplate (KafkaTemplate as well) received Micrometer observation support. Maybe something similiar has to be done for Pub/Sub ?
The text was updated successfully, but these errors were encountered: