-
Notifications
You must be signed in to change notification settings - Fork 2
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
reason of rating #3
Comments
Even though having this kind of information shown in nagios/icinga/… could be useful, I'd say "no" due to several reasons:
|
the status field in icinga2 seems to be much bigger than in icinga/nagios etc... It would be still nice to have some more information there. It could be an "verbose" version of the status... A lot of checks has a verbose version of the output :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it would be nice to know, what was the reason for a score. I mean, if I use --warn B --crit C and the check is "CRITICAL" or "WARNING" then it would be nice to know what is the reason not beeing A. It is possible to get such information with the API of Qualys?
(it is more feature request than issue)
The text was updated successfully, but these errors were encountered: