Reliable Insights

Sometimes users will not access Prometheus's UI directly, instead using another URL. How do you make this work?

The Prometheus web UI, such as the expression browser, depends on it being accessed on the same URL on which Prometheus itself is listening. This is as Prometheus needs to know where assets such as Javascript are and what URL to use in any links or redirects. If Prometheus is behind a reverse proxy, particularly one where Prometheus is not at the root, this doesn't work so well.

The good news is that Prometheus has features to cover this exact use case, and the Alertmanager also has the exact same features. This is primarily configured by the --web.external-url flag.

Let's say you have Prometheus running on it's usual port, and Nginx installed with the following configuration:

http {
 server {
   listen 0.0.0.0:19090;
   location /prometheus/ {
     proxy_pass :9090/prometheus/;
   }
 }
}
events {
}

This configuration would serve Prometheus up on :19090/prometheus/, and Nginx will include the /prometheus/ prefix when passing on requests to Prometheus. To make this work you'd need to run Prometheus like:

prometheus --web.external-url :19090/prometheus/

You should be aware that with this external URL, the /prometheus/ path prefix will be required for all HTTP access to Prometheus. The /metrics will be on :9090/prometheus/metrics for example.

 

In reality you wouldn't just be serving up Prometheus up on a different port on the local machine as in this demonstration. It'll likely be via a more human-readable DNS name, and possibly with HTTPS and other features in use. The principles all remain the same though!

 

Have questions around Prometheus and proxies? Contact us.