Description
Describe the bug
There is a bug in go-grpc that prevents the NO_PROXY setting from being properly applied based on domain name values in the NO_PROXY string. See issue here. At this point it seems that they're aware of the issue and working on a fix but just wanted to socialize this to see if we might need a temp patch. Note: this bug does not apply to localhost based NO_PROXY settings
Proposed Patch:
We should likely use DialContext instead of NewClient in the configgrpc package until this is resolved.
Steps to reproduce
Set an HTTP/HTTPS proxy and use the otlp exporter with a domain name that matches an entry in your NO_PROXY
What did you expect to see?
Proxy setting to remain unset
What did you see instead?
HTTPS_PROXY applied
What version did you use?
v0.112.0