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
In #98 severity was introduced to metrics rules.
However there is a small bug in them. When metrics is absent over time. the value became equal to one. Which means severity became warning.
And this shouldn't be like that. We could easily miss that node goes down. Because usually we are not sending warnigs to pagerduty
-
No response
The text was updated successfully, but these errors were encountered:
We should adjust the way we calculate the severity for that rule.
Sorry, something went wrong.
No branches or pull requests
Bug Description
In #98 severity was introduced to metrics rules.
However there is a small bug in them. When metrics is absent over time. the value became equal to one. Which means severity became warning.
And this shouldn't be like that. We could easily miss that node goes down. Because usually we are not sending warnigs to pagerduty
To Reproduce
Environment
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: