We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The /lookup command should have a debug argument so that rule developers and maintainers can access matches in an non-intrusive way.
/lookup
debug
Ideally the lookup command in debug mode will return a list of files that were matched against the highest weighted rules.
For example:
+==============+==============+==========================+ | File | Matched Rule | Match Metadata | +==============+==============+==========================+ | Activate.ps1 | some_rule_1 | line {lineno} - {string} | +--------------+--------------+--------------------------+ | __init__.py | some_rule_2 | line {lineno} - {string} | +--------------+--------------+--------------------------+
Files that match some_rule_1 which has a weight of 10 will appear above files that match some_rule_2 that have a weight of 8
some_rule_1
10
some_rule_2
8
The text was updated successfully, but these errors were encountered:
This will need to wait for match information to be tracked in both mainframe and the clients.
Sorry, something went wrong.
jonathan-d-zhang
No branches or pull requests
The
/lookup
command should have adebug
argument so that rule developers and maintainers can access matches in an non-intrusive way.Ideally the lookup command in debug mode will return a list of files that were matched against the highest weighted rules.
For example:
Files that match
some_rule_1
which has a weight of10
will appear above files that matchsome_rule_2
that have a weight of8
The text was updated successfully, but these errors were encountered: