Promtail does not fully use http_path_prefix

[amiga23]

Describe the bug
when setting http_path_prefix e.g. "/promtail/"

$ curl http://promtail:3101/promtail/
<a href="/targets">See Other</a>.

To Reproduce
Steps to reproduce the behavior:

1. Start promtail docker image with http_path_prefix configured as "/promtail/"
2. curl promtail endpoint with /promtail/

Expected behavior
Promtail should answer with redirect to:
/promtail/targets
but it does redirect to /targets
so http_path_prefix seems to be implemented only half-way

Environment:

• Infrastructure: kubernetes (k3s with containerd instead of docker)
• Deployment tool: kustomize

Screenshots, Promtail config, or terminal output
n/a

[cyriltovena]

/cc @sandeepsukhani Can you take a look please ?

[stale]

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[kelceydamage]

Hi, I'm experiencing the same exact issue. http_path_prefix is not being respected by promtail internal forwarding.

[firmero]

Still same behavior, redirecting to /targets, also hrefs contain fixed paths not reflecting http_path_prefix.

[Rom888]

The same issue, can't expose using ingress.

[Apollo3zehn]

Same problem here. Exposing via NGINX on path http://server/promtail/targets is not working.

Edit: As a workaround, I let NGINX rewrite the urls:

    location /promtail/ {
        proxy_pass http://localhost:3200/;

        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;

        sub_filter_once off;
        sub_filter 'href="/' 'href="';
        sub_filter 'src="/' 'src="';
    }

[bsinou]

The issue is still there in grafana/promtail:2.3.0 docker image.
Should we open a new issue?

[amiga23]

@bsinou if you want to get it fixed, either create a pull request ;-) or open a new ticket. This ticket was closed automatically, so I guess no developer is reading this.