-
-
Notifications
You must be signed in to change notification settings - Fork 303
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 Observations integration for SQS/SNS by default #566
Comments
Hi @sondemar, thanks for bringing this up. We haven't really started looking into The main challenge I see for this is that the I'm not sure how Micrometer works, but if it relies on a similar mechanism as Log4J's What do you think? Thanks |
I think it should be possible as the Micrometer Tracing works also with reactive APIs. |
Hi @tomazfernandes. following the comment http://disq.us/p/2rko9pj from @marcingrzejszczak and documentation about ctx propagation https://micrometer.io/docs/contextPropagation what I understand is it will not work out of the box and there should be created a custom "context" mechanism to manage ContextSnapshot to interact with Thread values. |
Closed in favor of #646 |
Type: Feature
Is your feature request related to a problem? Please describe.
With a new version of Spring Boot 3.x tracing propagation by Sleuth integration is replaced with Micrometer integration and with the newest version Spring Cloud Sleuth does not support AWS (SQS) integration anymore.
Describe the solution you'd like
Integrate Spring Cloud AWS with Micrometer tracing so that tracing propagation works by default for SQS/SNS integration. The tracing SQS message headers get extracted from the message and a trace gets put into the context or tracing context is put into tracing headers for pushed SNS message by default
Describe alternatives you've considered
As an alternative it could be porting the functionality from the Spring Cloud Sleuth project.
Additional context
Please let me know if you need a contribution to the implementation.
The text was updated successfully, but these errors were encountered: