Self-host Grafana on a VPS
Dashboards and exploration for metrics, logs, and traces from any data source.
levelrail-cli templates deploy grafana --name my-grafanaSpecification
- Status
- Verified on arm64 with image tag 11.2.0
- Category
- Monitoring
- Services
- grafana
- Ports
- 3000
- Volumes
- 1
- Memory
- about 256 MiB
- arm64
- tested
- amd64
- image published
- Settings to fill in
- none
About Grafana
Dashboards and exploration for metrics, logs, and traces from any data source. Runs as a single container from the grafana image, listening on port 3000; data is kept in named volumes.
What it deploys
Grafana runs as one service in a single Compose app, listening on port 3000, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| grafana | grafana/grafana | 11.2.0 | 3000 | grafana_data -> /var/lib/grafana |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Verified. Verified on arm64 with image tag 11.2.0. Verified means our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 3000 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 1 secret is generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| grafana | GF_SECURITY_ADMIN_PASSWORD | Generated at deploy |
Install Grafana on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get grafana -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy grafana --name my-grafana
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Grafana.
Docs and upstream
More in Monitoring
- Grafana (Postgres)Grafana backed by Postgres instead of its default embedded SQLite, for multi-instance or external-DB setups.
- Grafana AlloyA telemetry collector that scrapes metrics and ships them to Prometheus-compatible, Loki or Tempo backends. This starts with a small pipeline that scrapes its own metrics and logs them; edit the config to forward data elsewhere.
- Grafana LokiA horizontally scalable log aggregation system that indexes labels, not full text, to keep storage cheap.
- Grafana MimirHorizontally scalable long term storage for Prometheus metrics, run here as one process on local disk. The install form carries mimir.yaml as an editable file.
- Grafana OTel LGTMAn all-in-one OpenTelemetry backend with an OTLP collector, Loki logs, Tempo traces, Prometheus metrics and Grafana in one container. The Grafana admin password is generated at install. OTLP ports are not published on the host, so send telemetry from other services in this project to otel-lgtm:4317 (gRPC) or otel-lgtm:4318 (HTTP).
- Grafana TempoDistributed tracing backend that stores traces on local disk and accepts OTLP over gRPC and HTTP. The install form carries tempo.yaml as an editable file.