Graphite
Connect a Graphite instance to Perch to view its metrics alongside your other data sources.
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 Graphite and fill in:
- Name: a label for this connection, like “Production Graphite”
- URL: the base URL of your Graphite web app (e.g.
https://graphite.example.com)
You can also mark one data source as the default.
URL format
Point Perch at the Graphite web application URL, not the Carbon receiver port:
https://graphite.example.com
It has to be publicly reachable
Perch blocks private and internal addresses, so localhost, container names like graphite:80, and LAN IPs won’t work. The web app needs a public address, or a public reverse proxy in front of it.
Authentication
There’s no auth field today, so the Graphite web app has to allow unauthenticated reads. If yours is behind basic auth, put a proxy in front that handles it before the request reaches Graphite. Built-in auth is on the roadmap.