Ruby agent release notesRSS

Fixes

• Fix issue when app_name is nil

  If the app_name setting ends up being nil an exception got generated and the application wouldn't run. This would notably occur when running a Heroku app locally without the NEW_RELIC_APP_NAME environment variable set. A nil app_name is now detected and an error logged specifying remediation.

Fixes

• Support for Apdex T in server side configuration

  For those using server side configuration the Ruby Agent now supports setting the Apdex T value via the New Relic UI.

• The RUM NRAGENT tk value gets more robustly sanitized to prevent potential XSS vulnerabilities

  The code that scrubs the token used in Real User Monitoring has been enhanced to be more robust.

• Refactoring of agent config code

  The code that reads the configuration information and configures the agent got substantially reorganized, consolidated, simplified, and made more robust.

Bug Fixes

• Fix edge case in RUM auto instrumentation where X-UA-Compatible meta tag is present but </head> tag is missing.

  There is a somewhat obscure edge case where RUM auto instrumentation will crash a request. The issue seems to be triggered when the X-UA-Compatible meta tag is present and the </head> tag is missing.

• Fixed reference to @service.request_timeout to @request_timeout in new_relic_service.rb. (Thanks to Matthew Savage)

  When a timeout occurred during connection to the collector an "undefined method request_timeout for nil:NilClass" would get raised.

• preserve visibility on traced methods.

  Aliased methods now have the same visibility as the original traced method. A couple of the esoteric methods created in the process weren't getting the visibility set properly.

• Agent service does not connect to directed shard collector after connecting to proxy

  After connecting to collector proxy name of real collector was updated, but ip address was not being updated causing connections to go to the proxy. Agent now looks up ip address for real collector.

• corrupt marshal data from pipe children crashing agent

  If the agent received corrupted data from the Reqsue worker child agent it could crash the agent itself. fixed.

• should reset RubyBench GC counter between polls

  On Ruby REE, the GC profiler does not reset the counter between polls. This is only a problem if GC could happen between transactions, as in, for example, out-of-band GC in Unicorn. fixed.

Fixes

• Prevent the agent from resolving the collector address when disabled.
• Fix for error collector configuration that was introduced during beta.

New Feature(s)

• Major refactor of data transmission mechanism. This enabled child processes to send data to parent processes, which then send the data to the New Relic service. This should only affect Resque users, dramatically improving their experience.

Bug Fixes

• Resolve issue with configuring the Error Collector when using server-side configuration.

Changes

• Moved Resque instrumentation from rpm_contrib to main agent. Resque users should discontinue use of rpm_contrib or upgrade to 2.1.11.

Fixes

• Replaced "Custom/DJ Locked Jobs" metric with three new metrics for monitoring DelayedJob: queue_length, failed_jobs, and locked_jobs, all under Workers/DelayedJob
• Fix allowing instrumentation of methods ending in '?' or '!'
• Limit scanning first 50k of the response in RUM auto-instrumentation.
• Fix keeping exception from being raised when when extracting metrics from SQL queries with non UTF-8 bytes

Fixes

• Bug fix when rendering empty collection in Rails 3.1+

Fixes

• Rails 3 view instrumentation

Fixes

• Improved Sinatra instrumentation
• Limit the number of nodes collected in long running transactions to prevent leaking memory