Lauri Tulmin

> because even string literals in Class.forName("io.opentelemetry.context.Context") are rewritten to the new shaded context type. Shading plugins try to rename everything that looks like a class name, usually you can...

@axeaneProjects extractor needs to be added before the `KafkaTelemetry` instance is built. If you need to pass information to the extractor you could use opentelemetry `Context` or perhaps add it...

FYI while this may work in the short term it is likely that we will break it when work on https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/8999 resumes.

You can use the opentelemetry sdk to create custom spans. See https://opentelemetry.io/docs/instrumentation/java/manual/#create-spans In your application add dependency to `opentelemetry-api` (you won't need other dependencies with the agent). When using with...

@MrSinisterX Agent renames opentelemetry api classes as to not conflict with application provided opentelemetry api.

@axeaneProjects From the code you pasted it is not possible to discern why it should be connected with produce or receive span, please give a better sample.

The problem with `receive` is that the trace ends when the receive method exits. When you call `Context.current()` after the `receive` the context won't contain the `receive` span. As @mateuszrzeszutek...

closing as the jdk bug has been fixed

[We'd welcome a contribution for this](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/ISSUES.md#contribution-welcome) to https://github.com/open-telemetry/opentelemetry-java-contrib repository

@RashmiRam as far as I can tell conductor is not a framework that you'd include in your application but a standalone application. Instrumenting such applications requires deep understanding of what...