Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility to configure http proxy on OtlpGrpcMetricExporter side #6194

Closed
alexandru-roman-db opened this issue Feb 5, 2024 · 4 comments
Closed
Labels
Feature Request Suggest an idea for this project

Comments

@alexandru-roman-db
Copy link

Is your feature request related to a problem? Please describe.
Possibility to configure http proxy on OtlpGrpcMetricExporter side

Describe the solution you'd like
Similar to the OtlpGrpcMetricExporter.setEndpoint method an additional one would be nice to be added so that the proxy configuration is reaching the OkHttpGrpcExporter

Additional context
Currently we are using another library provided by NewRelic but this reached it's end-of-life and their documentation is recommending to use OpenTelemetry instead.

With the suggested usage of the OpenTelemetry library, when the micrometer data is being sent the following error occurs: java.net.SocketTimeoutException: Connect timed out

@alexandru-roman-db alexandru-roman-db added the Feature Request Suggest an idea for this project label Feb 5, 2024
@jack-berg
Copy link
Member

Hi - I'm a maintainer for this project and also an engineer for new relic. Can you tell me a little bit about your configuration and why supporting forward proxy configuration would resolve your issue?

@breedx-splk breedx-splk added the needs author feedback Waiting for additional feedback from the author label Feb 6, 2024
@alexandru-roman-db
Copy link
Author

Hi @jack-berg , Thank you for you message. The entire organisation network is configured that all the trafic going to the Internet needs to be forwarded through the proxy (for security reasons) and without having a possibility to configure this on library the traffic to NewRelic is blocked. Personally, I would suggest to have at least the possibility (we as developers) to configure the proxy for such cases.

@github-actions github-actions bot removed the needs author feedback Waiting for additional feedback from the author label Feb 6, 2024
@jack-berg
Copy link
Member

Got it. Coincidentally, another issue (#6204) was just filed as well with essentially the same request. My comment may be interesting to you:

we could extend programatic configuration for these options. The trick will be figuring out how proxy config manifests in different http clients (like the jdk httpclient and okhttp clients we use) and exposing some sort of generic representation. I'm open to adding support for this if somebody wants to contribute it.

In the short term, you might consider exporting to a collector running the otlphttpexporter, which does support proxy configuration. The docs don't mention it - support was added recently and the option is sort of a "hidden option" at the moment. See this open-telemetry/opentelemetry-collector#5761 for more details.

The author of that issue mentioned they are working on preparing a PR.

@jack-berg
Copy link
Member

#6270 was merged and released in the 1.36.0 release, and added proxy support for the OTLP http exporters. This issue specifically mentions proxy support for the OTLP gRPC exporters, but I'm going to close, assuming that gRPC and http are interchangeable and that the reporter can switch to http.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Suggest an idea for this project
Projects
None yet
Development

No branches or pull requests

3 participants