Refusing to re-register DependencyDetection block with name 'grape'


I am using grape-newrelic to instrument a grape api, with the latest version of gems my new_relic.log reads the following:

Installing HTTPClient instrumentation
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : Installing deferred Rack instrumentation
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : Finished instrumentation
[12/18/14 11:07:09 -0500 apistaging01 (6272)] WARN : Refusing to re-register DependencyDetection block with name ‘grape’
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : Starting the New Relic agent in “staging” environment.
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : To prevent agent startup add a NEWRELIC_AGENT_ENABLED=false environment variable or modify the “staging” section of your newrelic.yml.
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : Reading configuration from config/newrelic.yml (/var/www/omniapi/releases/20141218160642)
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : Doing deferred dependency-detection before Rack startup
[12/18/14 11:07:09 -0500 apistaging01 (6272)] INFO : Starting Agent shutdown
[12/18/14 11:07:09 -0500 apistaging01 (13754)] INFO : Starting Agent shutdown

And now data is being passed over to newrelic.

The breaking change seemns to ocurr when updating from to

Hi @omnipaste, thanks for letting us know about this! Our Ruby engineers are exploring adding first-class Grape support to the agent, and it looks like our efforts are currently colliding with grape-newrelic. We’re going to look into how to avoid that in the future. In the meantime, you’ll want to stick with version 3.9.7 of the agent.

Well, I will love to use the build in support and drop the gem, can you
point me to some docs?

Hi @omnipaste, this support isn’t available yet, but you can keep an eye on our Ruby agent release notes to check if it has been released.

Hey @omnipaste - we’ve just released version 3.9.9 of the newrelic_rpm gem, which should no longer conflict with the newrelic-grape gem. Sorry again about that, and thanks for reporting this to us!