We're using kotlin coroutines for implementing async services. One issue that we've run into is properly persisting the current span when the executed code resumes on a different thread.
There are execution hooks available that are meant for setup and tear down of thread locals which are meant for this usage.
Problem Im facing is not knowing the proper way to attach / detach a span to the current thread. The other issue that comes to mind is how to handle active span mutations that are not managed by the execution hook ie. some instrumented code is executed which creates a new child span.
We're using kotlin coroutines for implementing async services. One issue that we've run into is properly persisting the current span when the executed code resumes on a different thread.
There are execution hooks available that are meant for setup and tear down of thread locals which are meant for this usage.
Problem Im facing is not knowing the proper way to attach / detach a span to the current thread. The other issue that comes to mind is how to handle active span mutations that are not managed by the execution hook ie. some instrumented code is executed which creates a new child span.