Issue: When I make a call to one of my endpoints the last traceId is being polluted by /actuator calls. I have added a predicate to remove the /actuator calls from observability however the SecurityContextServerWebExchange is still being traced and is using the same traceId as the last non /actuator endpoint hit.
I am using the AutoConfiguredOpenTelemetrySdk for creating the OpenTelemetry Bean
Dependencies
Comment From: bclozel
I think it is going to be hard to figure this one out without a minimal application reproducing the problem. Could you provide one, ideally only depending on Spring Security and Spring WebFlux? A traceId being reused usually points to a library not cleaning up the thread after an observation was finished. Working on a minimal sample should help a lot pointing in the right direction. Thanks!
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.