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

Consider splitting errors into fatal/error/warning/info #23

Open
tobez opened this issue Aug 15, 2012 · 0 comments
Open

Consider splitting errors into fatal/error/warning/info #23

tobez opened this issue Aug 15, 2012 · 0 comments

Comments

@tobez
Copy link
Owner

tobez commented Aug 15, 2012

Requested by Daniel Stirnimann:

Nonetheless, I think in the long term it could still make sense to
provide the granularity of different error levels such as ERROR, WARNING
and maybe INFO. For example: you have a buggy signer which leaves some
old RRSIGs by accident and your zone is not in an algorithm key rollover
state as described above. The operator has enabled the above new policy
check because some of his zones do have an algorithm key rollover at one
point in time. Without providing different error levels, the operator
will not detect this failure in the buggy signer.
Maybe you could just log such situations in the "verbose" output so that
an operator has the chance to detect them. Current verbose logging would
be marked as INFO and more serious none-errors could be marked as WARNING.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant