Lauri Tulmin

@trask I added a note to the javadoc that marks this as experimental. We'll sooner or later wish to introduce experimental APIs, we might as well start with this one...

@123liuziming could you verify whether this helps in your case

@danielcompton can you sign the cla?

Thanks, we have merged https://github.com/open-telemetry/opentelemetry-java-contrib/pull/1829 that fixes the issue.

We use request attributes to associate some of our own state with the request. You can work around this by excluding these attributes ```java JsonRender.addExcludedAttrs( "io.opentelemetry.javaagent.instrumentation.servlet.ServletHelper.AsyncListenerResponse", "io.opentelemetry.javaagent.instrumentation.servlet.ServletHelper.Context", "trace_id", "span_id"); ```

> It works. And do we has plan to support jfinal? auto excluded attrs above and get `http.route ` [We'd welcome a contribution for this](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/ISSUES.md#contribution-welcome)

Auto update OpenTelemetry SDK workflow probably fails because `secrets.OPENTELEMETRYBOT_GITHUB_TOKEN` is not available and it can't create a PR. Subsequent runs fail because the branch already exists. I'd be willing to...

As you mentioned the opentelemetry plugin in `grpc-java` provides only metrics. The grpc instrumentation here also provides traces so replacing it with what `grpc-java` has is not an option at...

@Mahoney since https://github.com/open-telemetry/opentelemetry-java-contrib/pull/1789 does not have a signed cla it can not be merged. We are open to alternative PRs for this issue.

> Is the exception with `NoSuchFieldError` `__opentelemetryVirtualField` fixed in latest version of OTEL Java Instrumentation? We are also seeing this with older version of OTEL Java Instrumentation and Java 25,...