You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using Opentelemetry in our application with an extended java agent. The extension is built as described here build.gradle
The actual issue we're facing is with proxy authentication, the same as described here open-telemetry/opentelemetry-java#6819. Since this is not yet supported and with Okhttp we can't just set the Proxy-Authorization header, we thought we could get around it by using the JDK http client.
I believe we're still missing something as when running the application it's still using the Okhttp client:
[otel.javaagent 2025-02-27 16:51:50:774 +0100] [OkHttp https://target-url/...] ERROR io.opentelemetry.exporter.internal.http.HttpExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to authenticate with proxy
java.io.IOException: Failed to authenticate with proxy
at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.kt:476)
...
Suppressed: java.io.IOException: Failed to authenticate with proxy
... 22 more
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
We're using Opentelemetry in our application with an extended java agent. The extension is built as described here build.gradle
The actual issue we're facing is with proxy authentication, the same as described here open-telemetry/opentelemetry-java#6819. Since this is not yet supported and with Okhttp we can't just set the Proxy-Authorization header, we thought we could get around it by using the JDK http client.
We tried configuring it in the extension:
but this doesn't affect the java agent jar, which seems to include only the Okhttp sender.
As a last resort (which is really not ideal), we tried forking the instrumentation repo and added the jdk sender to the java agent tooling referring to open-telemetry/opentelemetry-java#5703
I believe we're still missing something as when running the application it's still using the Okhttp client:
Do you have any suggestion? Thank you.
Sorry for the duplicate open-telemetry/opentelemetry-java#7164 - wasn't sure where it would be best to post
Beta Was this translation helpful? Give feedback.
All reactions