There's some work needed to be done to properly propagate an OTel Context across a coroutine and its coroutine-context changes. This would involve having to change the way every Kotlin coroutine is launched in the project so that it checks for an existing OTel Context (if any) and then proceeds to transform it into part of the newly launched coroutine's context.
We can automate this with bytecode instrumentation, so this issue is to work on an auto-instrumentation that takes care of it so that users wouldn't have to change the way they launch coroutines.
There's some work needed to be done to properly propagate an OTel Context across a coroutine and its coroutine-context changes. This would involve having to change the way every Kotlin coroutine is launched in the project so that it checks for an existing OTel Context (if any) and then proceeds to transform it into part of the newly launched coroutine's context.
We can automate this with bytecode instrumentation, so this issue is to work on an auto-instrumentation that takes care of it so that users wouldn't have to change the way they launch coroutines.