Self-host Grafana Tempo with Levelrail
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.
- Authorgrafana
- LicenceAGPL-3.0-only
- Memory256 MiB
- Services1
How to self-host Grafana Tempo
-
Pull the images
One image is pulled on your server.
Show images
grafana/tempo:2.8.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 3200, 4317, 4318.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Send OTLP traces to port 4317 (gRPC) or 4318 (HTTP) and add this address as a Tempo data source in Grafana.
Grafana Tempo requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3200, 4317, 4318
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Grafana Tempo. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Grafana Tempo docs page.
Deploy Grafana Tempo your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Grafana Tempo from the CLI
levelrail-cli templates install tempo --name my-tempo Deploy Grafana Tempo with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/tempo/install \
-d '{
"name": "my-tempo"
}' Grafana Tempo configuration
Grafana Tempo services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| tempo | grafana/tempo:2.8.2 | 3200, 4317, 4318 | data -> /var/tempo |
Grafana Tempo environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 3200, 4317, 4318
- Volumes
- 1 named mount: data -> /var/tempo
Grafana Tempo FAQ
How much memory does Grafana Tempo need?
The catalog lists about 256 MiB of memory for Grafana Tempo.
Does Grafana Tempo run on arm64?
For Grafana Tempo, arm64 support is not confirmed; amd64 is unknown.
What licence is Grafana Tempo under?
Grafana Tempo is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Grafana Tempo need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Grafana Tempo use?
Grafana Tempo listens on ports 3200, 4317 and 4318 inside the stack.
Where does Grafana Tempo keep its data?
In a named volume: data mounted at /var/tempo.
Can I deploy Grafana Tempo on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Grafana Tempo, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image grafana/tempo:2.8.2 is what you deploy there.