accessing mimir-distributed with a subpath /mimir #8361

DontWanna1 · 2024-06-13T09:27:06Z

DontWanna1
Jun 13, 2024

I try to deploy the lgtm-distributed helm chart on a k3s cluster.

I can access mimir on / just fine
I can modify the grafana: section to serve a subpath

 ingress:
   enabled: false
   annotations:
   labels: {}
   path: /grafana
   hosts:
     - myhost.com
 grafana.ini:
   server:
     protocol: http
     domain: myhost.com
     root_url: "%(protocol)s://%(domain)s:%(http_port)s/grafana"
     serve_from_sub_path: true

The noteworthy part is root_url: "%(protocol)s://%(domain)s:%(http_port)s/grafana", which tells grafana to properly redirect (or something)
3. I can configure mimirs ingress to listen at /mimir, however, when trying to curl `curl myhost.com/mimir' I receive:

<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.25.5</center>
</body>
</html>

While reading through: https://github.com/grafana/mimir/blob/main/operations/helm/charts/mimir-distributed/values.yaml
I noticed the line 2956:

location = / {
            return 200 'OK';
            auth_basic off;
          }

I recon that there needs to be some information on how to handle the additional path.

How can I do this?

Best Regards

dimitarvdimitrov · 2024-06-14T10:00:54Z

dimitarvdimitrov
Jun 14, 2024
Maintainer

I think you're looking for these two config options

api:
  # (advanced) HTTP URL path under which the Alertmanager ui and api will be
  # served.
  # CLI flag: -http.alertmanager-http-prefix
  alertmanager_http_prefix: <string> | default = "/alertmanager"

  # (advanced) HTTP URL path under which the Prometheus api will be served.
  # CLI flag: -http.prometheus-http-prefix
  prometheus_http_prefix: <string> | default = "/prometheus"

you can change them to /mimir/prometheus and /mimir/alertmanager. FYI this was an issue for mimitool until recently; the fix will be in mimirtool 2.13 #8018

2 replies

DontWanna1 Jun 14, 2024
Author

Thank you for your reply.
First, I dod something complicated that worked:

mimir:
  nginx:
    nginxConfig:
      serverSnippet: |
        location /mimir/api/v1/push {
          if ($request_uri ~ ^/mimir/(.+)$) {
            set $new_request_uri "/$1";
          }
          set $distributor lgtm-distributed-mimir-distributor-headless.lgtm.svc.cluster.local.;
          proxy_pass      http://$distributor:8080$new_request_uri;
          #return 200 $new_request_uri;
          #auth_basic off;
        }

Second, how can apply the api.prometheus_http_prefix modification in the context of helm charts?

DontWanna1 Jun 14, 2024
Author

While I found occurences of template "mimir.prometheusHttpPrefix" in the values.yaml, the path I am interested about has no mention of it:

location = /api/v1/push {
              set $distributor {{ template "mimir.fullname" . }}-distributor-headless.{{ .Release.Namespace }}.svc.{{ .Values.global.clusterDomain }};
              proxy_pass      http://$distributor:{{ include "mimir.serverHttpListenPort" . }}$request_uri;
            }

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

accessing mimir-distributed with a subpath /mimir #8361

{{title}}

Replies: 1 comment 2 replies

{{title}}

{{title}}

{{title}}

Select a reply

accessing mimir-distributed with a subpath /mimir #8361

DontWanna1 Jun 13, 2024

Replies: 1 comment · 2 replies

dimitarvdimitrov Jun 14, 2024 Maintainer

DontWanna1 Jun 14, 2024 Author

DontWanna1 Jun 14, 2024 Author

DontWanna1
Jun 13, 2024

Replies: 1 comment 2 replies

dimitarvdimitrov
Jun 14, 2024
Maintainer

DontWanna1 Jun 14, 2024
Author

DontWanna1 Jun 14, 2024
Author