Open Frapschen opened 1 year ago
This appears to be the expected behavior. The ot
propagator will only inject 64-bit trace IDs for compatibility purposes. This could probably use better documentation, particularly a warning around this potential scenario where a system using the ot
propagator for outbound traffic is also responsible for generating the trace ID. It would need a 64-bit trace ID generator, which I don't believe currently exists.
Using ot propagator occur error
I want to use ot propagator, but find it can't parse trace id from upstream service. I use
instrumentation/google.golang.org/grpc/otelgrpc/example
to test it. The config.go I modified(add a&ot.OT{}
toNewCompositeTextMapPropagator
):then run the main.go in server dir and run the main.go with only call
callSayHello()
in client dir. I get the servier side log:the client side log:
I find that the client side get a error trace id.