-
Notifications
You must be signed in to change notification settings - Fork 40.5k
-
Notifications
You must be signed in to change notification settings - Fork 40.5k
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
Boot 3.0.8 -> 3.0.9 regression trace issue with Kafka Consumers #36592
Comments
This sort of problem is rarely caused by Spring Boot itself and I'd recommend spending some time downgrading individual components to determine the cause. In this case, it appears to be Please report this to the Micrometer team. |
FYI I actually think this problem is Spring Cloud Stream Kafka. If I just update spring cloud bom the trace IDs are lost. If this was an issue with micrometer losing tracing between threads it would affect everywhere but doesn't Will raise with spring cloud stream ... |
🤷 With this change to the pom.xml: diff --git a/pom.xml b/pom.xml
index db92f6f..e94c9ec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -5,7 +5,7 @@
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
- <version>3.0.8</version>
+ <version>3.0.9</version>
<!--version>3.0.7</version-->
</parent>
<groupId>uk.co.ii</groupId>
@@ -16,6 +16,7 @@
<properties>
<java.version>17</java.version>
<spring-cloud.version>2022.0.1</spring-cloud.version>
+ <micrometer.version>1.10.8</micrometer.version>
</properties>
<dependencies>
<dependency> This is the logging:
|
@wilkinsona happy to take your steer but it's not as clear cut because if you use 3.0.9 and micrometer 1.10.8 but also upgrade to <spring-cloud.version>2022.0.3</spring-cloud.version> it also breaks:
If this was a fundamental micrometer problem between threads then this would break other areas which I've actually tested this via a spring controller and all is fine
I'm fairly sure the micrometer team will point me to spring cloud streams ... |
Hi,
When upgrading from Boot 3.0.8 to Boot 3.0.9 we've noticed trace IDs going missing in our Kafka consumers. https://github.com/davidmelia/spring-boot-kafka-consumer-tracing/tree/boot_3.0.9_trace_issue illustrates this issue.
Using boot 3.0.8 and running http://localhost:8080/sendMessage you get
which is great. Update to boot 3.0.9 and the final tid disappears. tracing is lost
The consumer is quite simple https://github.com/davidmelia/spring-boot-kafka-consumer-tracing/blob/boot_3.0.9_trace_issue/src/main/java/com/example/demo/consumer/TestMessagesConsumer.java but the delay element is the part that loses the tid - I assume this is a bug in the threading trace context stuff?
Thanks
The text was updated successfully, but these errors were encountered: