We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. How can I configure this agent to use a proxy when connecting to the internet.
I tried to configure :httpc with proxy settings in my app like so:
:httpc
config/releases.exs
:httpc.set_options(proxy: {{'http://www.myproxy.com`, 3138}, []})
But I get the error in my logs
{ "application":"my-app","env":"prod","level":"ERROR", "message":"new_relic_agent - preconnect: (failed_request) {:failed_connect, [{:to_address, {'collector.newrelic.com', 443}}, {:inet, [:inet], :timeout}]}", "mfa":"{NewRelic.Logger, :handle_cast, 2}", "service":"pixel","timestamp":"2023-08-11T07:53:55.013Z" }
Describe the solution you'd like The node.js agent has an environment variable that can be configured for this purpose. NEW_RELIC_PROXY_URL
NEW_RELIC_PROXY_URL
Describe alternatives you've considered Should this agent be patched so the proxy settings are read in the lib/new_relic/init.ex file ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
How can I configure this agent to use a proxy when connecting to the internet.
I tried to configure
:httpc
with proxy settings in my app like so:config/releases.exs
But I get the error in my logs
Describe the solution you'd like
The node.js agent has an environment variable that can be configured for this purpose.
NEW_RELIC_PROXY_URL
Describe alternatives you've considered
Should this agent be patched so the proxy settings are read in the lib/new_relic/init.ex file ?
The text was updated successfully, but these errors were encountered: