home / images / tempo

Tempo

Grafana's distributed tracing backend. Prometheus-style economics for span storage.

Tempo (AGPL-3.0) is Grafana Labs''s traces backend. Deliberately simple: ingest OpenTelemetry/Jaeger/Zipkin spans and store them cheaply on S3/GCS/MinIO — no index on fields, lookup by trace ID only. Pair with Loki (logs) and Prometheus (metrics) for the "LGTM" observability stack. Pick it over Jaeger when storage cost is the dominant concern and you drive trace lookups from a logs-first workflow (log line → trace_id → Tempo).

category observability pulls 115.3M upvotes 0
SECURITY
A
best image
PULSE
F
score 24.62

Pulse score (60d)

0–100 composite · daily

Pulls growth (60d)

aggregate across all variants · daily

Pulse breakdown

F · 24.6/100 · snapshot 2026-11-14 04:03 UTC what is Pulse? →
Security average
83%
avg Rodeo grade across variants: 1.60 / 4.0 (A=4, F=0)
Rebuild recency (90d)
40%
23 of 40 images rebuilt in last 90d
Commits (90d)
0%
0 commits in last 90 days on GitHub
GitHub stars
0%
HN mindshare (90d)
0%
0 HN story mentions in last 90d

Each bar is this project's percentile among all 152 CE projects for that signal — 80% means it beats 4 out of 5 projects on that axis. Grade is an equal-weighted composite. Reddit mindshare lands here next; HN already contributes.

Which image should you pull?

top 5 of the project, ranked by current Rodeo score
#1
by grafana · 115.2M pulls · 39 MB · 2-arch · pushed 28d ago
▸ pull command docker pull grafana/tempo:3.0.4
NOW
A
100
ADDED
A
27d ago
OPEN CVES
0 / 0 / 0
C / H / M
Pull →
#2
by grafana · 115.2M pulls · 38 MB · 2-arch · pushed 24d ago
▸ pull command docker pull grafana/tempo:2.10.9
NOW
A
100
ADDED
A
24d ago
OPEN CVES
0 / 0 / 0
C / H / M
Pull →

What the herd is saying

No comments yet. Be the first.