Skip to content

Latest commit

 

History

History
 
 

example

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
docker-compose
docker-compose
 
 
helm
helm
 
 
tk
tk
 
 
readme.md
readme.md
 
 

readme.md

Examples

These folders contain example deployments of Tempo. They are a good resource for getting some basic configurations together.

Tempo Query

Note that even in the single binary deploys a second image named tempo-query is being deployed. Tempo itself does not provide a way to visualize traces and relies on Jaeger Query to do so. tempo-query is Jaeger Query with a GRPC Plugin that allows it to speak with Tempo.

Tempo Query is also the method by which Grafana queries traces. Notice that the Grafana datasource in all examples is pointed to tempo-query.

Docker Compose

The docker-compose examples are simpler and designed to show minimal configuration. This is a great place to get started with Tempo and learn about various trace discovery flows.

  • local storage
    • At its simplest Tempo only requires a few parameters that identify where to store traces.
  • s3/minio storage
    • To reduce complexity not all config options are exposed on the command line. This example uses the minio/s3 backend with a config file.
  • Trace discovery with Loki
    • This example brings in Loki and shows how to use a log flow to discover traces.

Jsonnet/Tanka

The jsonnet examples are more complex and show off the full range of configuration available to Tempo. The Helm and jsonnet examples are equivalent. They are both provided for people who prefer different configuration mechanisms.

  • single binary
    • A single binary jsonnet deployment. Valuable for getting started with advanced configuration.
  • microservices
    • Tempo as a set of independently scalable microservices. This is recommended for high volume full production deployments.

Helm

The helm examples are more complex and show off the full range of configuration available to Tempo. The Helm and jsonnet examples are equivalent. They are both provided for people who prefer different configuration mechanisms.

  • single binary
    • A single binary jsonnet deployment. Valuable for getting started with advanced configuration.
  • microservices
    • Tempo as a set of independently scalable microservices. This is recommended for high volume full production deployments.