-
Notifications
You must be signed in to change notification settings - Fork 36
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
JMS coralationId autoconfigure #219
Comments
I have the same problem with Spring Boot 3.0.5. |
We don't have instrumentations in tracing (except for kotlin really). I guess this should be done either in Micrometer for JMS native support or in Spring JMS for Spring based support. |
I have the same issue. Before with Sleuth, everything worked out of the box with JMS. |
Spring Boot 3.1.1 still not working. Folks, have you any workaround for this? |
The Jakarta JMS instrumentation is being contributed under micrometer-metrics/micrometer#4007; please review the observations and their KeyValues to check that they fit your use cases. |
Done via micrometer-metrics/micrometer#4007 |
Due the migration of sluth to micrometer, where can I find a parameter to automatically set the
traceId and spanId to the JMS message.
Previously, this was the configuration metter:
spring.sleuth.messaging.jms.enabled
Do I need to configure of exectutors for that? Can you give me a hint?
The text was updated successfully, but these errors were encountered: