Skip to content
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

change of syslog severity #228

Open
thl-cmk opened this issue Jan 1, 2022 · 0 comments
Open

change of syslog severity #228

thl-cmk opened this issue Jan 1, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@thl-cmk
Copy link

thl-cmk commented Jan 1, 2022

At the moment syslog messages are send like this

  • Files (potentially) vulnerable > Severity alert
  • Files mitigated > Severity notice
  • "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.

@xeraph xeraph self-assigned this Jan 2, 2022
@xeraph xeraph added the enhancement New feature or request label Jan 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants