Open lieberlois opened 3 months ago
if you add the tenant_id it works
mimir.rules.kubernetes "local" {
address = "http://mimir-ruler:8080"
tenant_id = "anonymous"
}
@clayton-cornell @tacole02 I see both alloy and metrics mentioned in this one. Which of you would be best to take on the assignment? Thanks!
At first glance, it appears more alloy-related. @clayton-cornell what do you think?
Yes, this is Alloy docs. I'll get it into the queue.
URL
https://grafana.com/docs/alloy/latest/reference/components/mimir/mimir.rules.kubernetes/
Feedback
alloy-infra-nrg9d alloy ts=2024-08-12T07:09:20.593144112Z level=error msg="starting up component failed, will retry" component_path=/ component_id=mimir.rules.kubernetes.default err="error GET /prometheus/config/v1/rules: unrecoverable error response: server returned HTTP status 401 Unauthorized: no org id"
With a minimal configuration like this
I get the error message as can be seen above. When port-forwarding to mimir-nginx and accessing the same path "/prometheus/config/v1/rules" in the browser, everything works fine. Mimir seems to have multitenancy enabled by default however I plan to not use it. Please extend the docs on how to configure this properly.
When using the mimir-distributed helm chart, it seems to work when pointing the mimir.rules.kubernetes component to the mimir-nginx service instead :)