-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat(matchexpressions): expressions can reference target JFR event type IDs #735
feat(matchexpressions): expressions can reference target JFR event type IDs #735
Conversation
/build_test |
Workflow started at 12/6/2024, 3:14:08 PM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ |
/build_test |
Workflow started at 12/6/2024, 3:50:45 PM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ |
caaa21b
to
3136928
Compare
3136928
to
329fec6
Compare
/build_test |
Workflow started at 12/19/2024, 4:33:24 PM. View Actions Run. |
No GraphQL schema changes detected. |
No OpenAPI schema changes detected. |
CI build and push: All tests pass ✅ |
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
See #733 (comment)
Related to #727
Related to #548
Description of the change:
See #733 (comment)
Motivation for the change:
Enables the creation of match expressions that evaluate the JFR event types available on a given target JVM. This probably isn't very useful for Stored Credentials, but for Automated Rules it will couple well with #733 , as well as with custom application-level JFR events. It becomes possible to define Automated Rules that use a preset or custom event template containing framework- or application-level events, and only activate on targets where those event types are actually present. For example, a Rule can be created that matches Quarkus applications which have the
quarkus-jfr
extension enabled.How to manually test:
./smoketest.bash -O
quarkus-jfr
extension, so if these two PRs are combined then the Quarkus-specific events referenced in that comment can be used. Otherwise, an event type ID likejdk.CPULoad
can be used to test the expression evaluation.