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

Misleading availability alerts #154

Closed
nsklikas opened this issue Sep 13, 2023 · 1 comment
Closed

Misleading availability alerts #154

nsklikas opened this issue Sep 13, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@nsklikas
Copy link
Contributor

Enhancement Proposal

The KratosUnavailable-multiple alert rule (https://github.com/canonical/kratos-operator/blob/main/src/prometheus_alert_rules/kratos_unavailable.rule#L11) is misleading in the sense that it is triggered any time more than 1 units are unavailable.

IMHO the granularity of our availability alert rules (we have 4 levels of availability) does not make much sense and I fail to see what they offer in terms of deployment availability.
After discussing it with @shipperizer I tend to agree that our alerts should be based on percentages of availability.
It is very different when 1 out of 3 units and when 1 out of 20 units is available, it is also very different when 1 out of 3 units is unavailable and when 1 out 20 is unavailable. With the current alerts it is impossible to tell these cases apart and both would yield the same alerts. If our alerts were based on percentages, one alert would offer a much clearer view of the problem.

@nsklikas nsklikas added the enhancement New feature or request label Sep 13, 2023
@syncronize-issues-to-jira
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/IAM-488.

This message was autogenerated

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

No branches or pull requests

2 participants