Thread terminated with exception when running specs with webmock about newrelic-ruby-agent

[rachelleahklein]

Hi, @mehyedes.

By default, the Ruby agent will report cloud vendor metadata to New Relic during its initial connect. You can disable checks for cloud vendor metadata via endpoints such as these via our utilization configuration options.

Thanks for reaching out, and let me know if this helps.

[rachelleahklein]

Hi @Hirurg103! Thanks for reaching out!

For questions about using/configuring the agent, we generally recommend working with our Support team, which can be reached directly though support.newrelic.com.

[Hirurg103]

Hi @rachelleahklein , thank you for the fast reply!

OK, I will contact Support team and paste there what they say

[rachelleahklein]

Sounds good. I will go ahead and close this issue. Thanks again!

[Hirurg103]

There are two ways to stop newrelic agent to send data to newlelic collector:

1. Add ENV['NEW_RELIC_MONITOR_MODE'] = 'false' in config/environments/test.rb
2. Set monitor_mode: false for the test environment in config/newrelic.yml (this is the default option when you generate newrelic config for the first time)

See New Relic documentation for monitor_mode option to get more details

[mehyedes]

Hi @rachelleahklein
I am wondering why the ruby agent needs to request 169.254.169.254 and metadata.google.internal at all for self hosted environments.
We have noticed that those outgoing requests have been affecting our application since they were trying to go through the proxy, so they don't fail early enough, but take ages to time out causing our processes to get stuck.
Please correct me if I am wrong.

[mehyedes]

Thank you for the link @rachelleahklein , I did not know about those options.
Will make sure to configure them to avoid this behavior.