End of life notification: As of January 26, 2015, New Relic will no longer accept data from Ruby agent versions prior to 3.5.3.
These agent versions use an out-of-date protocol when communicating with New Relic's data collection services, and many also contain a potential security issue where they may incorrectly send sensitive data to New Relic's servers.
To take the fullest advantage of New Relic's latest features, enhancements, and important security patches, New Relic strongly recommends that you update your Ruby agent to the latest version. For more information about agent updates, refer to the Ruby agent release notes.
Verify your Ruby agent version
To verify which Ruby agent version your apps currently use:
- From the New Relic UI, select (account dropdown) > Account settings > Connected agents.
- Optional: Sort by Oldest agent version.
- Look for Ruby apps that are earlier than version 3.5.3.
Update the Ruby agent
To verify the current Ruby agent version available:
- From the New Relic UI, select (account dropdown) > Account settings.
- From the Account information section, review the latest Ruby agent version.
- Select the link to the update instructions.
In general, to update to the latest Ruby agent version:
If you use bundler to manage your application's dependencies, then run:
bundle update newrelic_rpm
If you do not use bundler, then run:
sudo gem update newrelic_rpm
For correct instrumentation of New Relic on JRuby, use:
- New Relic Ruby agent version 126.96.36.199 or higher
- JRuby version 1.7.0 or higher
Otherwise, if your application has no transactions and you are using JRuby, you will not be able to see your CPU metrics. This was due to a bug in JRuby, where Process.times returned wall clock time instead of elapsed CPU time. That bug was fixed as of New Relic’s Ruby agent 188.8.131.52 and JRuby 1.7.0.
For more help
Additional documentation resources include: