Prometheus

Connect a Prometheus instance to Perch so you can view it alongside your other metrics.

Data sources are early days

This integration is still young. Right now a data source is just a name and a URL, with no authentication and no private addresses. Perch reaches it over the public internet with no credentials attached. Auth and private-network support are planned, but not here yet, so treat this as experimental.

Adding a connection

Go to Data Sources in the sidebar and click Add Data Source. Select Prometheus and fill in:

  • Name: a label for this connection, like “Production Prometheus”
  • URL: the base URL of your Prometheus instance (e.g. https://prometheus.example.com)

You can also mark one data source as the default. Save it, and Perch can test the connection by hitting Prometheus’s /-/healthy endpoint.

URL format

Use the base URL with no trailing slash. Perch appends the API paths itself:

https://prometheus.example.com

It has to be publicly reachable

Perch blocks private and internal addresses, so localhost, container names like prometheus:9090, and LAN IPs won’t work. The instance needs to be reachable on a public address. If yours isn’t, put it behind a public reverse proxy first.

Authentication

There’s no auth field today, so the Prometheus instance you point at has to allow unauthenticated reads. If it sits behind basic auth or a bearer token, you’ll need a proxy in front that handles auth before the request reaches Prometheus. Built-in auth is on the roadmap.