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
{{ message }}
Repository navigation
Reading Kafka messages is not reflected in the Application Insights as requests since upgrading to Spring boot 4 #4613
A <topic-name> process request is created when application receives a message.
Custom events published in the same thread have the operation_Id and operation_parentId filled based on the W3C traceparent header in the Kafka message.
Actual behavior
The requests are not present anymore. The custom events have the fields empty.
The example shows that the OpenTelemetry spans are no longer created with valid traceId / spanId. This makes the SpanContext invalid, so the tracing is not continued in BytecodeUtilImpl.
System information
SDK Version: 3.7.7
Application Server type and version (if applicable): Spring boot 4.0.2
A new version 3.7.8 was released. It is in sync with upstream OpenTelemetry Java Instrumentation 2.26.1. Can you try the new version and see if you still have the issue?
As issue #4577 was not resolved in 3.7.8 I was not able to migrate any of our services to Spring Boot 4.x and deploy them.
I have retested with the reproduction app I mentioned in the issue and it seems it is not fixed.
Activity
trask commentedon Feb 9, 2026
This should get resolved once we update to the latest OpenTelemetry Java Instrumentation.
nielsvanthof commentedon Mar 18, 2026
Is there a schedule for when a newer version will be released?
xiang17 commentedon Apr 5, 2026
A new version 3.7.8 was released. It is in sync with upstream OpenTelemetry Java Instrumentation 2.26.1. Can you try the new version and see if you still have the issue?
apokralipsa commentedon Apr 10, 2026
As issue #4577 was not resolved in 3.7.8 I was not able to migrate any of our services to Spring Boot 4.x and deploy them.
I have retested with the reproduction app I mentioned in the issue and it seems it is not fixed.
apokralipsa commentedon Aug 4, 2026
The issue seems to be resolved in 3.7.9 and we have successfully migrated to Spring Boot 4.x