near-zero intrusive tracing for golang about jaeger HOT 4 CLOSED

I am not aware of another way in Go, since it has no equivalent to thread-local storage. Even with thread local storage, given that Go highly encourages the use of goroutines, the context still needs to be transferred from one goroutine to another (similar problem exists in Java).

Note that Google, for all the lessons they learnt from Dapper, says:

https://blog.golang.org/context

At Google, we require that Go programmers pass a Context parameter as the first argument to every function on the call path between incoming and outgoing requests. This allows Go code developed by many different teams to interoperate well. It provides simple control over timeouts and cancelation and ensures that critical values like security credentials transit Go programs properly.

from jaeger.

Thanks for answering. That makes sense. Could you also shed more insight about java? That is also something we need to support as well.

from jaeger.

opentracing-java has recently added support for in-process context propagation into the main API, I suggest reviewing that & the corresponding docs (specifically around "active span"). We have not yet upgraded Jaeger Java client to that version.

from jaeger.

Thanks a lot.

from jaeger.