TiloBox
Back to directory
Grafana Tempo project preview

Grafana Tempo

High-scale, cost-effective distributed tracing backend requiring only object storage.

LicenseAGPL-3.0
GitHub stars6.8k
Last commit1 weeks ago
Tags6 topics
GrafanaDistributed TracingOpentelemetryDevops InfrastructureS3 TracingGolang
Overview

Why consider Grafana Tempo?

Grafana Tempo is an open-source, high-scale distributed tracing backend. Written in Go, it ingests traces from OpenTelemetry, Jaeger, Zipkin, and OpenTracing, storing petabytes of traces directly in cheap object storage (S3, GCS) without Elasticsearch.

Guided learning

Learn Grafana Tempo by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Grafana Tempo

Grafana Tempo links Prometheus metrics and Loki logs directly to span traces for instant full-stack root cause debugging.

Running with Docker

bash
1docker run -d \
2 --name tempo \
3 -p 3200:3200 -p 4317:4317 \
4 grafana/tempo:latest

Grafana Tempo is licensed under the GNU AGPL-3.0 license.

Related tools

More options with a similar category or technology profile.

Grafana Tempo FAQs

Grafana Tempo is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Grafana Tempo is listed under the AGPL-3.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Grafana Tempo is listed as an alternative to Jaeger. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.