Skip to content

Latest commit

 

History

History
61 lines (46 loc) · 2.29 KB

readme.md

File metadata and controls

61 lines (46 loc) · 2.29 KB
Raw

Jsonnet/Tanka

Congratulations! You have successfully found the jsonnet/tanka examples. These examples are meant for advanced users looking to deploy Tempo in a microservices pattern. If you are just getting started might I recommend the docker-compose examples. The docker-compose examples also are much better at demonstrating trace discovery flows using Loki and other tools.

If you're convinced this is the place for you then keep reading!

Initial Steps

The Jsonnet is meant to be applied to with tanka. To test the jsonnet locally requires:

  • k3d > v1.6.0
  • tanka > v0.12.0
k3d create --name tempo \
           --publish 16686:80

export KUBECONFIG="$(k3d get-kubeconfig --name='tempo')"

Next either deploy the microservices or the single binary.

Microservices

The microservices deploy of Tempo is fault tolerant, high volume, independently scalable. This jsonnet is in use by Grafana to run our hosted Tempo offering.

# double check you're applying to your local k3d before running this!
tk apply tempo-microservices

Single Binary

The Tempo single binary configuration is currently setup to store traces locally on disk, but can easily be configured to store them in an S3 or GCS bucket. See configuration docs or some of the other examples for help.

# double check you're applying to your local k3d before running this!
tk apply tempo-single-binary

View a trace

After the applications are running check the load generators logs

kc logs synthetic-load-generator-???
...
20/03/03 21:30:01 INFO ScheduledTraceGenerator: Emitted traceId e9f4add3ac7c7115 for service frontend route /product
20/03/03 21:30:01 INFO ScheduledTraceGenerator: Emitted traceId 3890ea9c4d7fab00 for service frontend route /cart
20/03/03 21:30:01 INFO ScheduledTraceGenerator: Emitted traceId c36fc5169bf0693d for service frontend route /cart
20/03/03 21:30:01 INFO ScheduledTraceGenerator: Emitted traceId ebaf7d02b96b30fc for service frontend route /cart
20/03/03 21:30:02 INFO ScheduledTraceGenerator: Emitted traceId 23a09a0efd0d1ef0 for service frontend route /cart

Extract a trace id and view it in your browser at http://localhost:16686/trace/<traceid>

Clean up

k3d delete --name tempo