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

Ensure all alerts correctly work when Mimir is deployed using the read-write deployment mode #3366

Closed
pracucci opened this issue Nov 2, 2022 · 1 comment · Fixed by #3626, #3627, #3628, #3710 or #3716
Assignees

Comments

@pracucci
Copy link
Collaborator

pracucci commented Nov 2, 2022

We should check all Mimir alerts 1-by-1, to ensure all of them correctly work (e.g. metrics are correctly queried) when Mimir is deployed in read-write deployment mode.

For example, any alert querying metrics with the container label matcher may not work (because container names are different). We could also consider a linter failing CI if anyone is using container label matcher in alerts.

@pracucci
Copy link
Collaborator Author

pracucci commented Nov 22, 2022

Also, the MimirGossipMembersMismatch alert doesn't work with read-write deployment mode because mimir-write.*|mimir-read.*|mimir-backend.* is missing from the configured ring_members.

Edit: fixed in #3489.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment