-
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
Setup prometheus-rules in Mimir #2521
Comments
prometheus-operator does not support mimir, we need to check grafana-operator |
The grafana agents supports that out of the box https://gigantic.slack.com/archives/C05AUBA75Q9/p1685709315899309 |
We know grafana-agent supports this and we now have an app for it. |
Review this giantswarm/grafana-agent-app#3, release and deploy it on gauss |
Also related giantswarm/prometheus-meta-operator#1309 |
Prometheus Rules are setup in mimir thanks to the grafana agent in flow mode (currently deployed by hand) using the following command:
with configmap.yaml being: agent:
configMap:
content: |
mimir.rules.kubernetes "local" {
address = "http://mimir-ruler.mimir.svc:8080/"
}
controller: deployment # defaults to daemonset which is not useful for our use case That way, prometheus rules CR are transformed by the grafana agent to prometheus rules sent to the mimir ruler. In addition, we deployed the mimir alertmanager and a datasource to make sure we can see the alerts. What's left:
Questions:
|
Rules are missing labels that are added by external labels when using remote write. All slo alerts should be grouped by them:
instead of
|
@giantswarm/team-atlas could you take a look at this issue? :) |
Done |
Mimir currently runs on
gauss
and do ingest metrics from other Prometheus servers (#2266 #2265).In order to replace the current Prometheus setup we need to move the Prometheus Rules evaluation from Prometheus Server to Mimir.
The text was updated successfully, but these errors were encountered: