This is documentation for the next version of Grafana Tempo documentation. For the latest stable release, go to the latest version.

Open source

Set up Tempo

To set up Tempo, you need to:

  1. Plan your deployment
  2. Deploy Tempo
  3. Test your installation
  4. (Optional) Configure Tempo services

Plan your deployment

How you choose to deploy Tempo depends upon your tracing needs. Tempo has two deployment modes: monolithic or microservices.

Refer to Plan your deployment to determine the best method to deploy Tempo.

Note

Tempo v3.0 microservices mode requires a Kafka-compatible system (such as Apache Kafka, Redpanda, or WarpStream). Monolithic mode (target: all) does not require Kafka. For more information, refer to the Deployment modes documentation.

Deploy Tempo

After you have decided the best method, you can deploy and set up Tempo.

Grafana Tempo is available as a pre-compiled binary, OS-specific packaging, and Docker image.

Refer to Deploy Tempo for instructions for deploying using Kubernetes and deploying locally.

Test your installation

After Tempo is deployed, you can validate Tempo by visualizing traces data:

These visualizations test Kubernetes with Tanka and Linux procedures. They don’t check optional configuration you have enabled.

(Optional) Configure Tempo services

Explore features by learning about available features and configurations.

If you would like to see a simplified, annotated example configuration for Tempo, the Introduction to MLTP example repository contains a configuration for a monolithic instance.