Add proxy config guide for EDOT #354
Conversation
|
|
||
| ### Java SDK | ||
|
|
||
| If you’re using Java SDK, you must configure Java system properties using the Java Virtual Machine (JVM). Refer to [Troubleshooting Java SDK proxy issues](../../troubleshoot/ingest/opentelemetry/edot-sdks/java/proxy-issues.md) for more information. |
There was a problem hiding this comment.
The link will work after I merge this PR.
|
|
||
| ## Proxy settings for EDOT SDKs | ||
|
|
||
| With the exception of Java SDK, EDOT SDKs use the `HTTP_PROXY / HTTPS_PROXY` settings from environment variables and require no extra configuration. |
There was a problem hiding this comment.
They seem to work fine for EDOT Python using the http/protobuf exporter but the grpc (default) one ignores them.
There was a problem hiding this comment.
Thanks for catching that!
Could you give me an example of how to configure gRPC proxy settings for the Python SDK?
|
|
||
| ## Proxy settings for EDOT SDKs | ||
|
|
||
| With the exception of Java SDK, EDOT SDKs use the `HTTP_PROXY / HTTPS_PROXY` settings from environment variables and require no extra configuration. |
There was a problem hiding this comment.
EDOT Node.js does not support HTTP_PROXY / HTTPS_PROXY / NO_PROXY currently.
Though you likely don't need the references: nodejs/node#58980 is a tracking issue for Node.js core support for these envvars -- which would, at least initially, require usage of NODE_USE_ENV_PROXY=1 to have Node.js processes turn these on.
Alternatively, EDOT Node.js could look into adding custom support for handling these envvars without relying on core Node.js support.
There was a problem hiding this comment.
@trentm Is there a manual workaround users could use as of now?
This PR adds documentation to help users configure proxy settings when using EDOT components.
The new proxy configuration guide: