-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Gateway traceid broken generation #3375
Comments
@ArtyomKazlanzhi can you please try using the latest versions of the libraries and retry? Usually, it's a matter of updating Spring Boot to 3.0.4. It carries the latest of Micrometer and Reactor unless you specify the versions on your own, in which case you also should bump. If using the latest versions you still see the issue, it's best if you prepare an isolated reproducer that we can work with. |
@chemicL I have tried to update the dependencies to the latests, trace id and span id are no more the same, they are generated correct, but they no more displayed in the logs |
its very unpredictable after upgrading to spring boot 3, same code produces traceId sometimes and sometimes not, not sure wats issue, this code issue i faced in spring cloud gateway where in a gateway filter i m trying to log something
|
@ArtyomKazlanzhi the README in the repository you provided mentions |
@github4sanjay without a reproducer it won't be possible to help. I would consider reporting this to the relevant Spring portfolio project if it is a functionality of that project. |
This problem re-appeared for me, I created #3584 with a simple reproducer. |
I'm working with Spring boot 3.01, micrometer tracing, bridge brave, spring cloud gateway
Found on the web that I can populate logs with traceId and spanId if to add reactor-core 3.5.3
and by adding
Hooks.enableAutomaticContextPropagation();
It really helps, but for some reason it breaks generating the trace id, for the first request to the gateway it generates a new one, then with every new request TraceContext using the same trace id over and over, except the span id, it's a new one every time (like it should be)
The text was updated successfully, but these errors were encountered: