traceId / spanId generated are changed post WebClient call

[syedyusufh]

We are using ReactorNettyHttpTracing with our Spring Web + Spring WebFlux + Spring Cloud Sleuth application. The traceId / spanId generated are getting changed post the WebClient call.

Spring Boot v2.6.1 and Spring Cloud v3.1.0

How do we retain the same traceId and spanId for the entire Spring Web request?

    @Bean
    public ReactorNettyHttpTracing reactorNettyHttpTracing(HttpTracing httpTracing) {
        return ReactorNettyHttpTracing.create(httpTracing);
    }

    WebClient.builder()
            .clientConnector(new ReactorClientHttpConnector(tracing.decorateHttpClient(httpClient)))
            .defaultHeader(HttpHeaders.CONTENT_TYPE, MediaType.APPLICATION_JSON_VALUE)
            .filters(exchangeFilters -> { 
                exchangeFilters.add(exchangeFilter.logRequest());
                exchangeFilters.add(exchangeFilter.logResponse());
            }).build();

[marcingrzejszczak]

Have you created the WebClient as a bean?

[syedyusufh]

Yes, it is created as a bean.

To be more precise with the behavior, since our application is Spring Web + Spring WebFlux, we do have a ControllerAdvice that is invoked to log the request payload; then the service layer makes the WebClient call and responds back a Mono from the RestController. On the way back, there is another ControllerAdvice to log the response.

Tried checking the traceId / spanId on the Mono using doOn***** side effects and they match the one initially found as part of the Spring Web ControllerAdvice. The new traceId / spanId is just after the call returns back from WebFlux to Web (ControllerAdvice)

[marcingrzejszczak]

Can you create a small sample (Maven & Java) that replicates this problem?

[syedyusufh]

Sure thing, please allow a day or two to get back without the actual application (functional) code.

Thanks

[syedyusufh]

Please try the below, you should be able to see the traceId / spanId changed post the WebClient call

https://github.com/syedyusufh/sleuth-web-webflux.git

[syedyusufh]

Hi @marcingrzejszczak

Kindly check and help

Thanks

[marcingrzejszczak]

Once I check I'll update this issue

[MohithMarisetti]

I'm having an almost similar issue with Spring cloud sleuth 3.x.x. I recently upgraded to Spring boot 2.6.6 and Sleuth 3.x.x. After the upgrade I see my HandlerInterceptor class is giving a different traceId in the afterCompletion() method. More info available here

@marcingrzejszczak @syedyusufh Any solution for this problem?

[Prithvi1994]

@marcingrzejszczak @syedyusufh We are facing the same issue when trying to upgrade spring boot to 2.6.6.

Any solution for this?

[syedyusufh]

@marcingrzejszczak can you please help check this issue? We still don't have a solution. As a temporary workaround, we are preserving the traceId through a request scoped bean in Spring Web.