First stab at supporting span propagation across boundaries. This commit provides the necessary functionality in order to instrument http servers and/or clients.
Under examples there is a dummy http client implementation that just logs to console.
The image above shows 3 http requests, first 2 are sent from the same span, so they have identical headers. But the third is sent from a child span, so it has a slightly different headers, but still sharing the same trace id (the first segment of the uber-trace-id).
Note the key uber-trace-id is just the default value provided by JaegerTracer, which is configurable of course, and also depends on which io.opentracing.Tracer implementation the user choose to provide.
gvolpe
commented
5 years ago
First stab at supporting span propagation across boundaries. This commit provides the necessary functionality in order to instrument http servers and/or clients.
Under examples there is a dummy http client implementation that just logs to console.
The image above shows 3 http requests, first 2 are sent from the same span, so they have identical headers. But the third is sent from a child span, so it has a slightly different headers, but still sharing the same trace id (the first segment of the
uber-trace-id).Note the key
uber-trace-idis just the default value provided byJaegerTracer, which is configurable of course, and also depends on whichio.opentracing.Tracerimplementation the user choose to provide.