Self-host Grafana Tempo on a VPS
Distributed 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.
levelrail-cli templates install tempo --name my-tempoSpecification
- Status
- Listed
- Category
- Monitoring
- Services
- tempo
- Ports
- 3200, 4317, 4318
- Volumes
- 1
- Memory
- about 256 MiB
- arm64
- unknown
- amd64
- unknown
- Settings to fill in
- none
- Listing
- Community template
About Grafana Tempo
Distributed 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.
What it deploys
Grafana Tempo runs as one service in a single Compose app, listening on ports 3200, 4317, 4318, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| tempo | grafana/tempo | 2.8.2 | 3200, 4317, 4318 | data -> /var/tempo |
Before you install
- CPU architecture. arm64 unknown. The scan could not read a manifest or the tag is chosen at install time. This is not a claim either way.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
Settings and environment
The catalog lists no environment variables for this template.
First run
- Send OTLP traces to port 4317 (gRPC) or 4318 (HTTP) and add this address as a Tempo data source in Grafana.
Install Grafana Tempo 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 tempo -
Install it
This template has an install form, so the CLI fills each setting from --env, a generated secret or its default.
levelrail-cli templates install tempo --name my-tempoTo put a service behind a domain at install, add
--domain SERVICE=HOST:levelrail-cli templates install tempo --name my-tempo --domain tempo=tempo.example.com
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 Tempo.
Docs and upstream
More in Monitoring
- 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 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 LokiA horizontally scalable log aggregation system that indexes labels, not full text, to keep storage cheap.
- 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 (Postgres)Grafana backed by Postgres instead of its default embedded SQLite, for multi-instance or external-DB setups.
- GrafanaDashboards and exploration for metrics, logs, and traces from any data source.