You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how legacy rules are related here. But I agree that mimirtool does not work with Mimir if Mimir is deployed with a non-default value for prometheus_http_prefix or alertmanager_http_prefix. Perhaps a command line flag next to --use-legacy-routes would help: --mimir-http-prefix defaulting to /prometheus. I believe it will be used here
Describe the bug
mimirtool 2.12
./mimirtool rules load rules.yml will not work if the mimir "prometheus_http_prefix:" is changed from "/prometheus" to "/"
Working:
Not working
It looks like the "POST Request" is wrong if the "--use-legacy-routes" parameter is used compared to "--no-use-legacy-routes"
WRONG POST request:
error="POST request to http://192.168.178.51:9009**/api/v1/rules/rules** failed
CORRECT Post request:
method=POST url="http://192.168.178.51:9009/prometheus**/config/v1/rules/rules**"
DEBU[0001] checking response status="202 Accepted"
To Reproduce
./mimirtool rules load ./rules.yml --address="http://192.168.178.51:9009" --id=anonymous --tls-insecure-skip-verify --use-legacy-routes --log.level="debug"
Expected behavior
It should be possible to use mimirtool to load ules with differnet prometheus_http_prefixes.
Environment
The text was updated successfully, but these errors were encountered: