-
Notifications
You must be signed in to change notification settings - Fork 0
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
Mimir testing #3578
Comments
I think it would be nice to run mimir continous testing (similar to loki canary) for e2e tests |
Yeah that's a nice idea :) |
I am running mimir continuous_test on grizzly with the following config:
and this renders the following metrics: and we could just use those alerts https://github.com/grafana/mimir/blob/f52911d917c8c52e0da6a59348a64dd7f7622072/operations/mimir-mixin-compiled/alerts.yaml#L1097 The only downside is that we need to wait for the next minor helm chart release or use a weekly version because this grafana/mimir#8654 is not yet released |
So what's the best plan of action IMO is to wait for the continuous testing to be a default config for our mimir before doing anything else. |
I think so yes, maybe we can have a pr ready with the alerts? The mixins contains some that could be useful |
@QuantumEnigmaa we decided in retro to use the chart version rc0 for now but keep the old image of mimir 2.13 |
All good with me 👍 |
We can start this again once we're done with multi-tenancy :) |
Taken over the dashboard PR giantswarm/dashboards#624 to close the epic |
Blocked waiting for reviews |
Continuous test is enabled on all MCs Added chart testing: Dashboard PR has been merged: Alert based on failures under review: Test procedure tbd: |
All is done. Thanks @hervenicol for the reviews |
Motivation
n order to raise our confidence in the stability of our observability platform and be sure that our ongoing work and releases won't negatively impact our observability platform operations we need to create extensive tests giving us early feedback loops. As mimir is one of our core components, we should make sure it's thoroughly tested.
Todo
Investigate some good initial test cases to give us feedback on the stability of a release on mimir on CI. This can be:
Implement those CI test cases
Investigate some good initial test cases to give us feedback on the stability of a release before releasing. This can be:
Implement those test cases
Make sure to stay with a set of minimal but valuable test cases, nothing to detailed and fancy.
Outcome
The text was updated successfully, but these errors were encountered: