For the (Active) Record, New Relic support for Rails 3.1 is here!

New RelicThe Brief Saga of Support for Rails 3.1

by Jon Guymon, Ruby Agent Engineer at New Relic

One of the best parts about working on the Ruby Agent is the community of people that I get to work with. The fact that the source for the Agent is freely available means that this community is almost infinitely expandable and we all get to collaborate on this great software. One brief example:

We have been eagerly awaiting the release of 3.1 and for good reason. The asset pipeline, in particular, is an ingenious way to organize a previously chaotic set of static assets. After spending some time addressing 3.1’s  change in the arity of the ActiveRecord log() method, which is used by Rails to report query performance in the development logs and by New Relic to collect metrics, we have officially rolled out the new 3.1 gem.

I want to extend a ‘thank you’ to the Rails community. In order to ensure that the Ruby Agent supports Rails 3.1 ahead of it’s official release, the community sprang into action. Many people got in touch with us to recommend ways to support for 3.1, but three people, in particular, went so far as to post patches on github:

Ben Hoskings
https://github.com/benhoskings/rpm/commit/96affa669337415cacee4b576b92d8e469f78b6b

David Genord II
https://github.com/xspond/rpm/commit/e609ef825ea45ca01ca0b0c7d4cffd92896090ce

Damien Mathieu
https://github.com/newrelic/rpm/commit/7af0982d4a3898be5a156aaa12fad027fb4330c2

We heard about Ben’s first, so his was the one we used, but they are all equally awesome.

The story goes on from here. There are currently twelve pull requests in my queue that I need to give some love to. Every one of them is appreciated, and every one of them is an example of why the Ruby Agent community is so great.

active_record_instrumentation

marketing@newrelic.com'

View posts by .

Interested in writing for New Relic Blog? Send us a pitch!