Trask Stalnaker

> I was wondering if we could get the best of both worlds by > > 1. Including the detector code in the agent > 2. Keeping it disabled by...

something similar to `otel.instrumentation..enabled=true`? (could be done entirely in the agent, without impacting resource providers themselves)

check out https://github.com/open-telemetry/opentelemetry-java/pull/3991, in particular: > notably this will prevent resource detection requests from being traced during agent startup due to https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/4642 cc @LikeTheSalad who is investigating options for suppress...

there's work in-progress which could unblock this: https://github.com/open-telemetry/opentelemetry-java/pull/5918

the reverse of this PR (moving from HttpURLConnection to OkHttp) was done a while ago in https://github.com/open-telemetry/opentelemetry-java/pull/3991 (when this code lived in that repository) I think really it's only a...

@rjbaucells can you integrate that change into your PR?

> only the okHttp sender implementation is using it right, so the okhttp sender is using it so that auto-instrumentation of OkHTTP won't capture those http requests in the same...

check out https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/9739

@jpkrohling probably want to move this issue to community repo?

@pjanotti here's a new copy under the GC account: https://docs.google.com/document/d/1dYdwRQVE3zu0vlp_lqGctNm0dCQUkDo2LfScUJzpuT8/edit?usp=sharing