Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable options for instrumented modules in newrelic.yml #614

Closed
drobnikj opened this issue Feb 8, 2021 · 4 comments
Closed

Disable options for instrumented modules in newrelic.yml #614

drobnikj opened this issue Feb 8, 2021 · 4 comments

Comments

@drobnikj
Copy link

drobnikj commented Feb 8, 2021

Feature Description

Added option into newrelic.yml config, which would disable instrumentation of required module in the app. There is no easy way(except one describe bellow), how you can disable the instrumented module. It is possible for example in Ruby agent(see the option to disable mongo).
The structure can be done the same as in Ruby or any other way.

{
 disable_mongo: true,
 disable_redis: true,
 ...
}

Describe Alternatives

I found one workaround here. But it didn't work if the required module in not in your code but in code of some dependency package.

Priority

Really Want

@michaelgoin
Copy link
Member

Thank you for the feature-request. We'll get this in front of the PM for consideration and prioritization.

We have an experimental branch where we have played with this concept but have not yet prioritized turning into official support. One thing worth noting as we consider this support... turning off any specific piece of instrumentation may currently cause transaction state loss. So the feature would need to come with some clear warnings / safety measures.

@workato-integration
Copy link

@bizob2828
Copy link
Member

This is still valid and we have talked about doing this a lot more recently. We need to get this prioritized as most other language have this ability

@bizob2828
Copy link
Member

We have added this here. This is a use at your own risk as context may not be propagated accordingly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done: Issues recently completed
Development

No branches or pull requests

3 participants