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
vmalert: vmalert_alerting_rules_error
should be a counter
#5160
Labels
Comments
hagen1778
added a commit
that referenced
this issue
Dec 6, 2023
See #5160 Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778
added a commit
that referenced
this issue
Dec 6, 2023
See #5160 Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778
added a commit
that referenced
this issue
Dec 6, 2023
See #5160 Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778
added a commit
that referenced
this issue
Dec 6, 2023
See #5160 Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778
pushed a commit
that referenced
this issue
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
vmalert exposes a gauge metric
vmalert_alerting_rules_error
which shows whether the current rule is failing or not. But it seems like a countervmalert_alerting_rules_error_total
would be more sufficient here, as it could show not only the state but also rate of failures. And also capture state changes between the scrapes, if any.Describe the solution you'd like
Would be great to convert gauge
vmalert_alerting_rules_error
to countervmalert_alerting_rules_error_total
. The change will require not only changes to vmalert, but also to dashboards and recommended alerting rules.Describe alternatives you've considered
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: