Ruby agent release notesRSS

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

• fix for cookie handling by End User Monitoring instrumentation

• deployments recipe change: truncate git SHAs to 7 characters
• Fixes for obfuscation of PostgreSQL and SQLite queries
• Fix for lost database connections when using a forking framework
• Workaround for RedHat kernel bug which prevented blocking reads of /proc fs
• Do not trap signals when handling exceptions

• Performance and stability improvements
• Restored compatibility with Ruby 1.8.6

• New slow SQL tracing feature
• New expanded browser tracing