Hopefully resolves
https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7124
Our kotlin coroutine instrumentation relies on a shaded copy of
`opentelemetry-extension-kotlin`. This doesn't work well when
application also uses `opentelemetry-extension-kotlin`, because the
shaded and unshaded copy store opentelemery context under different key.
This pr attempts to fix this by instrumenting
`opentelemetry-extension-kotlin` provided by the application so that it
would delegate to the one shaded inside the agent.
Co-authored-by: Mateusz Rzeszutek <mrzeszutek@splunk.com>
* kotlinx-coroutines-reactor context propagation
* extract context from reactor
* add generics
* muzzle
* actually use the context extracted from reactor
* test context propagation operator
* typo
* used named instead of namedOneOf
* instrument newCoroutineContext, remove reactor specific code
* revert changes
Lauri Tulmin
Anuraag Agrawal
Trask Stalnaker
Anuraag Agrawal