Document proxy configuration for Java SDK #2100
Conversation
🔍 Preview links for changed docs |
| -Dhttp.proxyHost=proxy.example.com \ | ||
| -Dhttp.proxyPort=8080 \ | ||
| -Dhttps.proxyHost=proxy.example.com \ | ||
| -Dhttps.proxyPort=8080 \ |
There was a problem hiding this comment.
I did expect this to not work, because to my knowledge the exporters use OkHttp3, which I thought would not respect these properties. However, according to this issue it should work. Did we test this?
There was a problem hiding this comment.
Hi Jonas! It should work as of this PR.
It was double-checked by @AlexanderWert and @SylvainJuge
| -Dhttps.proxyPort=8080 \ | ||
| ``` | ||
|
|
||
| ## Best practices |
There was a problem hiding this comment.
What about calling this "Testing" "Validation" or "Test your proxy"?
There was a problem hiding this comment.
In this case yes, it would make sense. I was trying to stick to the Troubleshooting topic structure we came up with: Symptoms - Resolution - Best practices (optional) - Resources (optional)
I'll be adding a lot more OTel troubleshooting topics in the future, so I wanted to keep them organized in more or less the same way.
This PR adds a troubleshooting guide to help users resolve proxy issues when using EDOT Java SDK. The guide explains that the Java SDK requires explicit JVM proxy config.