New Span being created for each HTTP request in OpenTracingServerFilter

[achatterjee104]

Expectation

Scenario 1:

1. There are 2 REST services - service-A and service-B
2. A request comes to service-A and its OpenTracingServerFilter creates a new span, say [trace-id=1, span-id=1]
3. service-A invokes service-B, waits for its response and then returns the consolidated result
4. service-B will get the request with [trace-id=1, span-id=1] and it should created its new span [trace-id=1, span-id=2] (since trace-id is already present)
5. At the end, there will be 2 spans (span-id=1 & span-id=2) as child of trace-id=1

Scenario 2:

1. There is a REST service with 2 endpoints - /books & /authors
2. A request comes to /books and its OpenTracingServerFilter creates a new span, say [trace-id=1, span-id=1]
3. /books endpoint internally invokes /authors endpoint (via a REST call), waits for its response and then returns the consolidated result
4. during /authors endpoint call, the OpenTracingServerFilter will get the request with [trace-id=1, span-id=1] and it should created its new span [trace-id=1, span-id=2] (since trace-id is already present)
5. At the end, there will be 2 spans (span-id=1 & span-id=2) as child of trace-id=1

Ref: This guide says "Whenever a Micronaut server receives a request, it creates a new span"

From Source Code

From OpenTracingServerFilter,

Tracer.SpanBuilder spanBuilder = continued ? null : newSpan(request, initSpanContext(request))

it seems to be creating new span everytime, irrespective of presence of existing trace-id.

Is my understanding correct?