Loki

Connect a Grafana Loki instance to Perch to view logs alongside your 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 Loki and fill in:

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

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

URL format

Use the base URL with no trailing slash:

https://loki.example.com

It has to be publicly reachable

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

Authentication

There’s no auth field today, so the Loki instance you point at has to allow unauthenticated reads. Grafana Cloud Loki and other setups that require a username plus API token aren’t supported yet, since Perch sends no credentials. Built-in auth is on the roadmap. For now, a public, unauthenticated Loki (or one behind an auth-handling proxy) is the way to go.