SpringBoot Server Spans do not follow OTEL semantic convensions?

[ross-paypay]

In my springboot application (instrumented with the java agent), I see 2 Server spans for each request.

1. A span generated from io.opentelemetry.tomcat-10.0 with a span name like GET /v1/foo
2. A span generated from org.springframework.boot with a span name like http get /v1/foo

The Tomcat span appears to be properly following OTEL semantic conventions, however the springboot generated span does not.

I have tried to disable the springboot instrumentation but doing so also affects the tomcat span information resulting in the span losing information (i.e. the span name becomes GET /**)

I was wondering if this is expected?
Is there any way to configure the java agent to only emit a single Server span that adheres to OTEL semantic conventions?

[laurit]

I'd guess that spans from org.springframework.boot are generated by micrometer tracing not otel. You are probably better off choosing one tracing solution.