Allow wildcards in Instrument profiling engine
#1435
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apangin
reviewed
Aug 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In this PR I introduce support for simple
*wildcards (both for class and method) in the event selector for theInstrumentengine. This is now valid:event=*.*event=*.<init>event=java.lang.Thread.*Related issues
#1421
Motivation and context
This feature is mainly aimed at testing extensively #1421. Instrumenting all methods in a run loading a considerable amount of classes will give us confidence about the changes.
How has this been tested?
make test-java -j TESTS=instrumentBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.