The parent-child relationship miss

[TanYuzhen]

Description

When I use the microservices system hotelReservations ( https://github.com/[TanYuzhen/hotelReservation](https://github.com/TanYuzhen/hotelReservation ) , and send a request as below:

#!/usr/bin/env bash
IN_DATE="2015-04-12"
OUT_DATE="2015-04-15"
LAT="38.0235"
LON="-122.095"
curl -v -X GET "http://10.106.122.121:5000/hotels?inDate=${IN_DATE}&outDate=${OUT_DATE}&lat=${LAT}&lon=${LON}" 

And I get the trace of the request shown as below:

Because the original of the hotelReservations microservices uses the opentracing SDK, I change it to use the opentelemetry SDK. However, the parent-child relationship is missing as the photo shows.

Environment

• OS: Ubuntu22.04
• Architecture: x86
• Go Version: 1.24
• opentelemetry-go version: v1.36.0

Steps To Reproduce

1. Use the microservices 'https://github.com/TanYuzhen/hotelReservation'
2. Send the request , get the trace as the photo shows
3. See error

Expected behavior

I want the search service, profile service is the children of frontend service, and the geo service, rate service is the children of search service.
How to fix that in my code?

[dmathieu]

Your service has a lot of required context. A simpler reproduction case would help in helping you.

This looks like a missmatch in the propagation headerd being used. Are you using W3C Trace Context in both cases ?

[TanYuzhen]

No, I didn't use W3C Trace Context in the photo's request, and I don't why the parent-child ship miss. And , the json of the trace shows that there had a invalid span

"warnings": [
                        "invalid parent span IDs=8af84832e5e1202a; skipping clock skew adjustment"
                    ]

And the span 8af84832e5e1202a doesn't exist in my trace.

[TanYuzhen]

And I get the log of the Client side such as frontend service as below:

[CLIENT] about to call Search, trace=abbe83a46d73eba1fd892005b0a6cfb9 span=274139f7dcba0c7d
[DEBUG] unary client interceptor executed: /search.Search/Nearby
[DEBUG] unary client interceptor executed: /reservation.Reservation/CheckAvailability
[DEBUG] unary client interceptor executed: /profile.Profile/GetProfile

The log of the child side of frontend such as search services as below:

[SEARCH] extracted trace=abbe83a46d73eba1fd892005b0a6cfb9 span=5a783c9afbf844a5 remote=false
[DEBUG] unary client interceptor executed: /geo.Geo/Nearby
[DEBUG] unary client interceptor executed: /rate.Rate/GetRates

We can see that the trace_id is the same, however the span of search service can't link the parent span in frontend service