-
Notifications
You must be signed in to change notification settings - Fork 9
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
Standardize and Improve Plugin Logs #1037
Conversation
df34d12
to
b55cec9
Compare
This PR adds INFO start/end logs to all the plugins except: npm, linguist, git, and github. Those plugins appear to be used by the other plugins during analysis and do not provide their own analysis metric so I chose to leave them without this INFO log. |
I'd still add it. They're not "top-level" plugins (they don't expose a default query), but it can still be useful for debugging to know when they're running. |
I agree with Andrew, the reason we did the work of adding parsing and per-plugin control through |
b55cec9
to
1aa715d
Compare
1aa715d
to
c569aa6
Compare
Signed-off-by: Kirill Usubyan <kusubyan@mitre.org>
c569aa6
to
f17ac19
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good Kirill, thanks!
Resolves #915
Standardize and add to the plugin logs for consistency, clarity, and increased utility for debugging.
All plugin queries produce an INFO level log "running
query_name
query" at start and INFO level "completedquery_name
query" at successful resolution. The linguist plugin is an exception and it logs queries at the DEBUG level because it produces thousands of logs due to repeatedis_source_file()
calls.All plugins which use the plugin engine to query other plugins also produce TRACE level logs at that point.