Replies: 1 comment
-
Hello, as you may have heard, we are transitioning away from using discussions to discuss feature requests. This is phrased as a question, and we'd like questions about grafana to go to our community forum. Feel free to make an issue if you cannot find a solution and would like to request the feature. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm having a heck of a time getting the above to work.
Previously, I was using
loki-distributed
, and the connection between Grafana and Loki worked when I enabled the ruler with appropriate S3 (Minio) backed storage.I recently stood up a new instance of Loki using the new
grafana/loki
Helm chart and moved my log collection to that. I was not worried about log history and didn't want to migrate, so I just created a new one. I pasted both the old and new values.yaml files below for reference.The new Loki instance is running and collecting logs. It has no problem acting as a Loki datasource for my Grafana instance is able to query all of the logs, however, I am unable to create alerts. When I attempt to save, I get the following error:
I tried using
cortextool
to see the rules for my loki instance (and to see if it's even running), and I get these messages:There isn't much in the Grafana documentation around the appropriate configuration needed for Grafana to create alerts, other than ensuring that I'm not using local storage. As best I can tell, I have S3 storage configured correctly, but there is no data in the bucket. I also don't see any pods that are running the ruler, are those now handled via the read/write nodes?
Do i have to pre-seed this ruler with a fake group, rule, or alert in order for Grafana to be able to add/edit alerts?
My old
loki-distributed
values.yaml:My new
loki
values.yamlBeta Was this translation helpful? Give feedback.
All reactions