We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CRITICAL
A clear and concise description of what the bug is.
Steps to reproduce the behavior:
SEVERITY flag wasn't updated as INFO when it previous developments in #190
SEVERITY
A clear and concise description of what you expected to happen.
Send VATZ liveness notification with INFO severity because people will assume this message as alert if notification would come with 'CRITICAL'
INFO
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered:
xellos00
Successfully merging a pull request may close this issue.
Checklist
Describe the bug
How to Reproduce
SEVERITY
flag wasn't updated as INFO when it previous developments in #190Expected behavior
Send VATZ liveness notification with
INFO
severity because people will assume this message as alert if notification would come with 'CRITICAL'Screenshots
The text was updated successfully, but these errors were encountered: