-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Allow JMS listener instrumentation [SPR-14683] #19247
Comments
Grenville Wilson commented I'm a user directly affected by this problem, since it prevents Spring Sleuth spans from propagating across JMS connections. I can confirm that this would resolve the issue I've been having with |
Ales Justin commented For OT I've just added such integration, which should imho handle any payload: |
Stéphane Nicoll commented Ales Justin this is very interesting. Can you extract the API that would make this possible without a full replacement as you're doing now? I can see a much more elegant solution if we change how the registry creates endpoints. Thoughts? |
Ales Justin commented Stéphane Nicoll yeah, was just thinking about this yday -- to provide a PR, but it was already 2am. :-) |
Jon Schneider commented We'll need the same feature for Micrometer. See this related issue. |
Superseded by #30335 |
Marcin Grzejszczak opened SPR-14683 and commented
In Spring Cloud Sleuth we would want to give the users a possibility to instrument all
@JmsListener
annotated methods in order to propagate tracing information. In the Issue Garry mentions thatCan we give the possibility of adding listeners / proxies / whatever to instrument the listeners?
For all incoming messages from JMS we would like to be able to do some pre processing and post processing (let's assume that the message arrived from a destination "foo").
Reference URL: spring-cloud/spring-cloud-sleuth#151 (comment)
2 votes, 9 watchers
The text was updated successfully, but these errors were encountered: