Micrometer trace HTTP request span propagation

We’ve noticed that child spans of HTTP requests were showing up as independent root traces after migrating Spring Cloud GCP to Spring Boot 3.0 (RC2).

In old Spring Cloud Sleuth, HttpTracing bean was enriched with HTTP request parsing. While in Micrometer BraveHttpRequestParser exists, it does not seem to be instantiated or injected into HttpTracing bean in Spring Boot autoconfiguration. In fact, HttpTracing bean configured in Spring Boot looks very minimalistic.

Is there a new mechanism through which we should be extracting existing trace information from HTTP headers?

[JoeWang1127]

Hi @jonatan-ivanov, thanks for your feedback, the @Observed works for me (with extra help from here). You can close the issue, thanks.

[jonatan-ivanov]

There are a few issues with the sample:

1. It is quite big, I’m not 100% sure what you are talking about
2. You are using Sleuth (Sleuth is for Boot 2, if you are using Boot 3 please use Micrometer Tracing)
3. You are using Brave’s API for things that you should be able to do with the Observation API (also with Micrometer Tracing)

However, compared with sleuth, the default span name is not the annotated method’s name, even change the name or value parameter doesn’t change the span name.

If you mean @NewSpan by this, that won’t work, that annotation is from Sleuth, it should not even be on your classpath (see the second point above). On the first screenshot, everything looks ok to me, if you want an additional span, you can use @Observed.