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

Add ability to whitelist auto instruments for non-controller classes #305

Open
J-Swift opened this issue Nov 13, 2019 · 2 comments
Open

Comments

@J-Swift
Copy link

J-Swift commented Nov 13, 2019

There is a way to blacklist files for auto instruments, but no way to whitelist non-controller classes. My use-case is that I'm working on a rails app that heavily utilizes Concerns. Since those are not 'controller classes' I don't get insight into some hot-spots. It would be nice to be able to specify these classes so that they can also be instrumented.

@ioquatix
Copy link
Contributor

This makes sense.

I guess we should allow users to specify more than just controller classes.

@m9
Copy link

m9 commented Feb 19, 2021

i second this, i have pretty same issue as @J-Swift do, and would be happy to get concerns(and other non-controller classes) instrumented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants