# Self-host 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.

- Page: https://levelrail.com/templates/tempo/
- JSON: https://levelrail.com/templates/tempo.json
- Category: Monitoring
- Licence: AGPL-3.0-only (Network copyleft (AGPL) license)
- Source: https://github.com/grafana/tempo
- Upstream docs: https://grafana.com/docs/tempo/latest/

## Requirements
- Memory: about 256 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 2.8.2

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| tempo | grafana/tempo | 2.8.2 | 3200, 4317, 4318 | data -> /var/tempo |

## Deploy

### CLI

```bash
levelrail-cli templates install tempo --name my-tempo
```

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain tempo=app.example.com.

### API

```bash
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"
  }'
```

Create a token in the dashboard first. Name, env and domains are the request fields.

## First run
1. Send OTLP traces to port 4317 (gRPC) or 4318 (HTTP) and add this address as a Tempo data source in Grafana.

## Questions

### 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.

Self-host Grafana Tempo, Grafana Tempo docker compose file, deploy Grafana Tempo on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
