-
Notifications
You must be signed in to change notification settings - Fork 97
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
Connection timeout connecting to collector.eu01.nr-data.net
#390
Comments
I've started getting this also, thanks for the fix |
I started getting this today as well on AWS ECS. |
This is now happening for me even with a 5_000ms timeotu set. |
Yeah, on AWS ECS I actually had to raise it all the way to |
For extra context there is a thread on the NewRelic discuss about this issue. Feel free to also let them know there. |
Whoops, didn't mean to close this one. I do think we need a better solution that's not opt-in so it's solved for every user, see some of the discussion here. tl;dr: let's provide a higher timeout just for collector communication and do a scan of the codebase to see if that could conflict with timeouts elsewhere (GenServer calls, for example). If anyone takes it on feel free to tag me |
just published https://hex.pm/packages/new_relic_agent/1.27.8 |
i am seeing this issue from Linode, Kamatera and Cloudcone as well. Is there any docs on how to increase the timeout in 1.27.8 ? |
Nope. Unfortunately, documentation has not been updated yet. But you can do this in your config: config :new_relic_agent,
httpc_request_options: [
connect_timeout: 13_000 # choose whatever number is suitable for you here
],
... |
Thanks @infinityfye, I have a PR sent for docs update hope that gets merge and is of use to others |
Closing in favor of #395 |
Describe the bug
I'm seeing the following error in my
tmp/new_relic.log
Changing the http timeout in
NewRelic.Util.HTTP
to 2000ms rather than 1000ms seems to remove the error.Would you accept a PR to increase, or make configurable the timeout? With the low timeout if the preconnect fails we don't get any transaction tracing at all.
Environment
Both locally and remote on Heroku.
elixir -v
):mix deps | grep new_relic_agent
):new_relic_agent 1.27.7
The text was updated successfully, but these errors were encountered: