All Versions
Latest Version
Avg Release Cycle
62 days
Latest Release
518 days ago

Changelog History
Page 10

  • v3.5.6 Changes

    • Use HTTPS by default

      The agent now defaults to using SSL when it communicates with New Relic's servers. By default is already configured New Relic does not transmit any sensitive information (e.g. SQL parameters are masked), but SSL adds an additional layer of security. Upgrading customers may need to remove the "ssl: false" directive from their newrelic.yml to enable ssl. Customers on Jruby may need to install the jruby-openssl gem to take advantage of this feature.

    • Fix two Resque-related issues

      Fixes a possible hang on exit of an instrumented Resque master process (, as well as a file descriptor leak that could occur during startup of the Resque master process.

    • Fix for error graph over 100%

      Some errors were double counted toward the overall error total. This resulted in graphs with error percentages over 100%. This duplication did not impact the specific error traces captured, only the total metric.

    • Notice gracefully handled errors in Sinatra

      When show_exceptions was set to false in Sinatra, errors weren't caught by New Relic's error collector. Now handled errors also have the chance to get reported back.

    • Ruby 2.0 compatibility fixes

      Ruby 2.0 no longer finds protected methods by default, but will with a flag.

      Thanks Ravil Bayramgalin and Charlie Somerville for the fixes.

    • Auto-detect Trinidad as dispatcher

      Code already existing for detecting Trinidad as a dispatcher, but was only accessible via an ENV variable. This now auto-detects on startup. Thanks Robert Rasmussen for catching that.

    • Coercion of types in collector communication

      Certain metrics can be recorded with a Ruby Rational type, which JSON serializes as a string rather than a floating point value. We now treat coerce each outgoing value, and log issues before sending the data.

    • Developer mode fix for chart error

      Added require to fix a NameError in developer mode for summary page. Thanks to Ryan B. Harvey.

    • Don't touch deprecated RAILS_ROOT if on Rails 3

      Under some odd startup conditions, we would look for the RAILS_ROOT constant after failing to find the ::Rails.root in a Rails 3 app, causing deprecation warnings. Thanks for Adrian Irving-Beer for the fix.

  • v3.5.5 Changes

    • Add thread profiling support

      Thread profiling performs statistical sampling of backtraces of all threads within your Ruby processes. This feature requires MRI >= 1.9.2, and is controlled via the New Relic web UI. JRuby support (in 1.9.x compat mode) is considered experimental, due to issues with JRuby's Thread#backtrace.

    • Add audit logging capability

      The agent can now log all of the data it sends to the New Relic servers to a special log file for human inspection. This feature is off by default, and can be enabled by setting the audit_log.enabled configuration key to true. You may also control the location of the audit log with the audit_log.path key.

    • Use config system for dispatcher, framework, and config file detection

      Several aspects of the agent's configuration were not being handled by the configuration system. Detection/configuration of the dispatcher (e.g. passenger, unicorn, resque), framework (e.g. rails3, sinatra), and newrelic.yml location are now handled via the Agent environment, manual, and default configuration sources.

    • Updates to logging across the agent

      We've carefully reviewed the logging messages that the agent outputs, adding details in some cases, and removing unnecessary clutter. We've also altered the startup sequence to ensure that we don't spam STDOUT with messages during initialization.

    • Fix passing environment to manual_start()

      Thanks to Justin Hannus. The :env key, when passed to Agent.manual_start, can again be used to specify which section of newrelic.yml is loaded.

    • Rails 4 support

      This release includes preliminary support for Rails 4 as of 4.0.0.beta. Rails 4 is still in development, but the agent should work as expected for people who are experimenting with the beta.

  • v3.5.4 Changes

    • Add queue time support for sinatra apps

      Sinatra applications can now take advantage of front end queue time reporting. Thanks to Winfield Peterson for this contribution.

    • Simplify queue time configuration for nginx 1.2.6+

      Beginning in version 1.2.6, recently released as a development version, the $msec variable can be used to set an http header. This change allows front end queue time to be tracked in New Relic simply by adding this line to the nginx config:

      proxy_set_header X-Queue-Start "t=${msec}000"

      It will no longer be necessary to compile a patched version of nginx or compile in the perl or lua module to enable this functionality.

      Thanks to Lawrence Pit for the contribution.

    • Report back build number and stage along with version info

      In the 3.5.3 series the agent would fail to report its full version number to NewRelic's environment report. For example it would report its version as 3.5.3 instead of or The agent will now report its complete version number as defined in newrelic_rpm.gemspec.

    • The host and the port that the agent reports to can now be set from environment vars

      The host can be set with NEW_RELIC_HOST and the port with NEW_RELIC_PORT. These setting will override any other settings in your newrelic.yml.

    • Fix RUM reporting to multiple applications

      When the agent is configured to report to multiple "roll up" applications RUM did not work correctly.

  • v3.5.3 Changes

    • Update the collector protocol to use JSON and Ruby primitives

      The communication between the agent and the NewRelic will not longer be marshaled Ruby objects, but rather JSON in the case of Ruby 1.9 and marshaled Ruby primitives in the case of 1.8. This results in greater harvest efficiency as well as feature parity with other New Relic agents.

    • Fix incorrect application of conditions in sinatra instrumentation

      The agent's sinatra instrumentation was causing sinatra's conditions to be incorrectly applied in some obscure cases. The bug was triggered when a condition was present on a lower priority route that would match the current request, except for the presence of a higher priority route.

  • v3.5.2 Changes

    • Simplified process of running agent test suite and documented code contribution process in GUIDELINES_FOR_CONTRIBUTING.
  • v3.5.1 Changes

    • Enabling Memory Profiling on Lion and Mountain Lion

    The agent's list of supported platforms for memory profiling wasn't correctly checking for more recent versions of OS X.

    • Fixed an arity issue encountered when calling newrelic_notice_error from Rails applications.

    • End user queue time was not being properly reported, works properly now.

    • Server-side configuration for ignoring errors was not being heeded by agent.

    • Better handling of a thread safety issue.

    Some issues may remain, which we are working to address, but they should be gracefully handled now, rather than crashing the running app.

    • Use "java_import" rather than "include_class" when require Java Jars into a JRuby app.

    Thanks to Jan Habermann for the pull request

    • Replaced alias_method mechanism with super call in DataMapper instrumentation.

    Thanks to Michael Rykov for the pull request

    • Fixed the Rubinius GC profiler.

    Thanks to Dirkjan Bussink

    • Use ActiveSupport.on_load to load controller instrumentation Rails 3.

    Thanks to Jonathan del Strother

    • Reduce the number of thread local reference in a particular high traffic method

    Thanks to Jeremy Kemper

  • v3.5.0 Changes

    • (Fix) RUM Stops Working After Agent Upgrade

    v3.4.2.1 introduced a bug that caused the browser monitor auto instrumentation (for RUM) default to be false. The correct value of true is now used

    • When the Ruby Agent detects Unicorn as the dispatcher it creates an INFO level log message with additional information

    To help customers using Unicorn, if the agent detects it (Unicorn) is being used as the dispatcher an INFO level log message it created that includes a link to New Relic online doc that has additional steps that may be required to get performance data reporting.

    • (Fix) In version 3.4.2 of the Ruby Agent the server side value for Apdex T was disregarded

    With version 3.4.2 of the agent, the value set in the newrelic.yml file took precedence over the value set in the New Relic UI. As of version 3.5.0 only the value for Apdex T set in the New Relic UI will be used. Any setting in the yaml file will be ignored.

    • Improved Error Detection/Reporting capabilities for Rails 3 apps

    Some errors are missed by the agent's exception reporting handlers because they are generated in the rails stack, outside of the instrumented controller action. A Rack middleware is now included that can detect these errors as they bubble out of the middleware stack. Note that this does not include Routing Errors.

    • The Ruby Agent now logs certain information it receives from the New Relic servers

    After connecting to the New Relic servers the agent logs the New Relic URL of the app it is reporting to.

    • GC profiling overhead for Ruby 1.9 reduced

    For Ruby 1.9 the amount of time spent in GC profiling has been reduced.

    • Know issue with Ruby 1.8.7-p334, sqlite3-ruby 1.3.0 or older, and resque 1.23.0

    The Ruby Agent will not work in conjunction with Ruby 1.8.7-p334, sqlite3-ruby 1.3.3 or earlier, and resque 1.23.0. Your app will likely stop functioning. This is a known problem with Ruby versions up to 1.8.7-p334. Upgrading to the last release of Ruby 1.8.7 is recommended. This issue has been present in every version of the agent we've tested going back for a year.

  • v3.5.0.1 Changes

    • (Fix) Due to a serious resource leak we have ended support for versions of Phusion Passenger older than 2.1.1. Users of older versions are encouraged upgrade to a more recent version.
  • v3.4.2 Changes

    • 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.

    • 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.

    • 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.

  • v3.4.2.1 Changes

    • 🛠 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.