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
Hi team. Currently the prometheus query path is hardcoded. This makes it difficult to utilize tools such as Mimir as this introduces /prometheus prefix to all API paths, and I imagine it's possible that other users are running their Prometheus server(s) behind a proxy with varying paths.
I'd propose a way to make this configurable, with the current value (/api/v1/query_range) as a default.
The text was updated successfully, but these errors were encountered:
Hi team. Currently the prometheus query path is hardcoded. This makes it difficult to utilize tools such as Mimir as this introduces
/prometheus
prefix to all API paths, and I imagine it's possible that other users are running their Prometheus server(s) behind a proxy with varying paths.I'd propose a way to make this configurable, with the current value (
/api/v1/query_range
) as a default.The text was updated successfully, but these errors were encountered: