You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"error": "Skipping broken jar file..." > Severity debug
I would like to have this changed a bit,
Files mitigated > change the configuration option --syslog-level info to --syslog-level notice to match the severity
"error": "Skipping broken jar file..." > Severity error, because this is an error, the option --syslog-level debug should then be changed from debug to error.
The Severity debug could be used in conjunction with the --trace option if need be.
Messages like "Running scan (10s): scanned 9119 directories, ..." could use the severity info.
The text was updated successfully, but these errors were encountered:
At the moment syslog messages are send like this
I would like to have this changed a bit,
--syslog-level info
to--syslog-level notice
to match the severity--syslog-level debug
should then be changed fromdebug
toerror
.The Severity debug could be used in conjunction with the
--trace
option if need be.Messages like "Running scan (10s): scanned 9119 directories, ..." could use the severity info.
The text was updated successfully, but these errors were encountered: