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

Programmatically disabling instrumentation on classpath #411

Open
breedx-splk opened this issue Jun 4, 2024 · 0 comments
Open

Programmatically disabling instrumentation on classpath #411

breedx-splk opened this issue Jun 4, 2024 · 0 comments

Comments

@breedx-splk
Copy link
Contributor

This is a tracking issue that follows up on this comment in #408.

Now that we've moved to the fancy new instrumentation API, we have a case where all instrumentation that is included at build-time should show up on the classpath at runtime in order to be disabled. There may be cases, however, where users want to programmatically disable some instrumentation at runtime based on configuration or something else (a probabilistic model, whatever the case may be).

It's perfectly reasonable to defer this until we have an actual ask from an end-user, but I wanted to make sure it had been captured.

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

1 participant