Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

query: Fix external prefix and add an e2e test for it #2800

Merged
merged 12 commits into from
Jul 2, 2020
70 changes: 70 additions & 0 deletions docs/operating/reverse-proxy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
---
title: Running Thanos behind a reverse proxy
type: docs
menu: operating
slug: /reverse-proxy.md
---

# Running Thanos behind a reverse proxy

Many times you would like to use a [reverse proxy](https://www.nginx.com/resources/glossary/reverse-proxy-server/) in front of Thanos. There are several reasons to use a reverse proxy such that SSL termination (serve Thanos over HTTPS) and basic authentication.
onprem marked this conversation as resolved.
Show resolved Hide resolved

## External Prefix and Route

Before continuing, lets first take a look at two cli flags provided by Thanos, `--web.external-prefix` and `--web.route-prefix`. The External Prefix is useful when you want to prefix all requests from UI with some path. Normally, the web UI would load all static assets from `/static/...`, do API calls on `/api/v1/...` etc. But if we use `--web.external-prefix="thanos"` the UI would prefix each request with `/thanos`. It would try to load all assets from `/thanos/static/...`, do API calls on `/thanos/api/v1/...` and so on. One thing to note here is that `--web.external-prefix` only prefixes the requests and redirects with the specified value, but Thanos is still listening on the root, not the specified sub-path i.e. the API is still accessible at `/api/v1/...` and not at `/thanos/api/v1`. This is where `--web.route-prefix` comes in. If you set `--web.route-prefix="thanos"` every route would get prefixed with the specified value. For example, the API will be accessible on `/thanos/api/v1`. As this is the most common use case when using the `--web.external-prefix`, the default value of `--web.route-prefix` is the value of `--web.external-prefix`.
onprem marked this conversation as resolved.
Show resolved Hide resolved

> Note: Using different values for `--web.external-prefix` and `--web.route-prefix` can lead to the web UI not working properly if it is accessed directly (without a reverse proxy).
onprem marked this conversation as resolved.
Show resolved Hide resolved

## Examples

Lets look into some example scenarios. All examples are using Nginx as a reverse proxy here.
onprem marked this conversation as resolved.
Show resolved Hide resolved

### Serving Thanos on a subdomain

Serving a Thanos component on the root of a subdomain is pretty straight-forward. Let's say you want to run Thanos querier behind a Nginx server, accessible on domain `thanos.example.com`. A basic Nginx configuration would look like this:
onprem marked this conversation as resolved.
Show resolved Hide resolved

```
http {
server {
listen 80;
server_name thanos.example.com;

location / {
proxy_pass http://localhost:10902/;
}
}
}

events {}
onprem marked this conversation as resolved.
Show resolved Hide resolved
```

### Serving Thanos on a sub-path

Things become a little tricky when you want to serve Thanos on a sub-path. Let's say, you want to run Thanos querier behind an Nginx server, accessible on the URL `http://example.com/thanos`. The Thanos web UI depends on it being accessed on the same URL as Thanos itself is listening. This is because the UI needs to know the URL from where to load static assets and what URL to use in links or redirects. If Thanos is behind a reverse proxy, particularly one where Thanos is not at the root, this doesn't work so well.
onprem marked this conversation as resolved.
Show resolved Hide resolved

To tackle this problem, Thanos provides a flag `--web.external-prefix`.

Let's say we have Thanos querier running on the usual port, we need Nginx running with the following configuration:
onprem marked this conversation as resolved.
Show resolved Hide resolved

```
http {
server {
listen 80;
server_name example.com;

location /thanos/ {
proxy_pass http://localhost:10902/thanos/;
}
}
}

events {}
onprem marked this conversation as resolved.
Show resolved Hide resolved
```

With this configuration, you can access Thanos querier on `http://example.com/thanos`. Notice that as we are using `http://localhost:10902/thanos/` as the reverse proxy target, every request path will be prefixed with `/thanos`. To make this work we need t run Thanos querier like
onprem marked this conversation as resolved.
Show resolved Hide resolved

```
thanos query --web.external-prefix="thanos"
```

It should be noted that now the `/thanos` path prefix would be required for all HTTP access to Thanos. The `/metrics` endpoint would be accessible at `http://localhost:10902/thanos/metrics`.
onprem marked this conversation as resolved.
Show resolved Hide resolved
2 changes: 2 additions & 0 deletions test/e2e/query_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,7 @@ func TestQueryExternalPrefix(t *testing.T) {
querierURL := urlParse(t, "http://"+q.HTTPEndpoint()+"/"+externalPrefix)

querierProxy := httptest.NewServer(e2ethanos.NewSingleHostReverseProxy(querierURL, externalPrefix))
onprem marked this conversation as resolved.
Show resolved Hide resolved
t.Cleanup(querierProxy.Close)

checkNetworkRequests(t, querierProxy.URL+"/"+externalPrefix+"/graph")
}
Expand Down Expand Up @@ -241,6 +242,7 @@ func TestQueryExternalPrefixAndRoutePrefix(t *testing.T) {
querierURL := urlParse(t, "http://"+q.HTTPEndpoint()+"/"+routePrefix)

querierProxy := httptest.NewServer(e2ethanos.NewSingleHostReverseProxy(querierURL, externalPrefix))
onprem marked this conversation as resolved.
Show resolved Hide resolved
t.Cleanup(querierProxy.Close)

checkNetworkRequests(t, querierProxy.URL+"/"+externalPrefix+"/graph")
}
Expand Down