OTLP endpoint proxying issue

[cap1kaden]

I have an issue where when connecting to the endpoint defined in the OTLP Exporter config, it doesn't respect the NO_PROXY configuration. The reason this happens is it forces the dns GRPC resolver, which resolves to multiple IP addresses and those addresses are checked against the NO_PROXY configuration. In my case the IP addresses aren't consistent so I can't just add those to NO_PROXY instead.

I can't seem to figure out a way to force the passthrough resolver, or explicitly force grpc.WithNoProxy() dial option. Adding the passthrough:// scheme breaks the OTLP Exporter config validation saying there are too many colons (http, https, and dns schemes work because they are trimmed).

Before looking into a solution for this, I just wanted to make sure nobody knows a way to solve this with the currently implementation. Thanks in advance!

[cap1kaden]

Came across this issue which discusses this interaction. The simplest solution seems like it'd be to add an option like no_proxy: true to the GRPC config which adds grpc.WithNoProxy() dial option. I think this is mainly an issue with using the Lambda Layer since that's [probably] the only time you would really have conflicts between the proxy settings for the collector and for other code (since they run in the same execution environment).

I did end up finding a workaround where I don't set the proxy environment variables in the Lambda configuration, but then set them in the main function (or in an init function). This of course isn't a great solution, but it works for now 🤷