New Relic v3.6.7 Release Notes
-
- Resque-pool support
Resque processes started via the resque-pool gem weren't recognized by the Ruby agent. The agent now starts correctly in those worker processes.
- Environment-based configuration
All settings in newrelic.yml can now be configured via environment variables. See https://newrelic.com/docs/ruby/ruby-agent-configuration for full details.
- Additional locking option for Resque (3.6.7.159)
There have been reports of worker process deadlocks in Resque when using the Ruby agent. An optional lock is now available to avoid those deadlocks. See https://newrelic.com/docs/ruby/resque-instrumentation for more details.
- HTTP connection setup timeout (3.6.7.159)
HTTP initialization in the agent lacked an appropriate timeout, leading to dropouts in reporting under certain network error conditions.
- Unnecessary requests from Resque jobs (3.6.7.159)
An issue causing Resque jobs to unnecessarily make requests against New Relic servers was fixed.
- Fix compatibility issues with excon and curb instrumentation
This release of the agent fixes a warning seen under certain circumstances with the excon gem (most notably, when excon was used by fog), as well as a bug with the curb instrumentation that conflicted with the feedzirra gem.
- Allow license key to be set by Capistrano variables
A license key can be passed via a Capistrano variable where previously it could only be in newrelic.yml. Thanks Chris Marshall for the contribution!
- Make HTTP client instrumentation aware of "Host" request header
If a "Host" header is set explicitly on an HTTP request, that hostname will be used for external metrics. Thanks Mislav Marohnić for the contribution!
- Fix ActiveSupport::Concern warnings with MethodTracer
Including NewRelic::Agent::MethodTracer in a class using Concerns could cause deprecation warnings. Thanks Mike Połtyn for the contribution!
- Fix Authlogic constant name
Code checking for the Authlogic module was using in the wrong case. Thanks Dharam Gollapudi for the contribution!