Open mishanchus opened 2 weeks ago
Having the same issue. Upvoting.
@mishanchus I managed to get it working. This is the ruler config in the helm chart, apparently the ruler
config you used (had the same issue) is broken in the helm chart:
loki:
rulerConfig:
# https://github.com/grafana/loki/issues/9114#issuecomment-1506620229
wal:
dir: /var/loki/ruler-wal
alertmanager_url: "http://mimir-nginx.mimir:80/alertmanager"
remote_write:
enabled: true
add_org_id_header: true
clients:
mimir:
url: http://mimir-nginx.mimir:80/api/v1/push
I found the config here so i assumed i have to switch to loki.rulerConfig
@JStickler If you point me to the right location i can contribute this to the docs 😄 👍
@lieberlois I'm not sure where exactly which docs topic(s) you want to update?
For the most part, the URL for a page in the documentation maps to the source files, so for example:
The source for the published page https://grafana.com/docs/loki/latest/setup/install/helm/install-monolithic/ Can be found in https://github.com/grafana/loki/tree/main/docs/sources/setup/install/helm/install-monolithic
The Helm reference topic https://grafana.com/docs/loki/latest/setup/install/helm/reference/ Is automatically generated from the template found in https://github.com/grafana/loki/tree/main/production/helm/loki/reference.md.gotmpl
The Loki configuration file https://grafana.com/docs/loki/latest/configure/#ruler Is automatically generated from code comments and the template found in https://github.com/grafana/loki/blob/main/docs/templates/configuration.template
Describe the bug Ruler remote_write does not work when auth_enabled: true
To Reproduce Steps to reproduce the behavior: Loki Distributed Helm chart, 0.76.1, loki.config contains "auth_enabled: true". Ruler config in loki.config section:
Ruler config in ruler section of values.yaml:
When the parameter auth_enabled: false metrics are writed correctly.
Expected behavior Metrics are written to the specified Prometheus server
Environment:
Screenshots, Promtail config, or terminal output Logs from the Ruler pod at startup. Prometheus will no longer be present in the logs. At the same time, it is clear that requests from rules are executed successfully.
When auth_enabled disabled there is success message in logs
After upgrade to 3.2.0 we get a useful message in the logs:
Prometheus works fine. And if you change the address to a non-existent one, the timeout error will be exactly the same