d1df5c56ca
* Migrate changes from Tempo PR Signed-off-by: Jack Baldry <[email protected]> * Updates to resolve conflicts * Move getting started files * Fix aliases * Merge remote-tracking branch 'origin/master' into jdb/2025-07-tempo-set-up-restructure Signed-off-by: Jack Baldry <[email protected]> * Discard changes to content/docs/tempo/next/sync.json * Add aliases Signed-off-by: Jack Baldry <[email protected]> * Fix some aliases Signed-off-by: Jack Baldry <[email protected]> * Updates from rebase * Apply suggestions from code review Co-authored-by: Jack Baldry <[email protected]> * Apply suggestions from code review Co-authored-by: Jack Baldry <[email protected]> * Update content/docs/tempo/next/set-up-for-tracing/instrument-send/set-up-collector/tail-sampling/policies-strategies.md Co-authored-by: Jack Baldry <[email protected]> * Fix links on tile page and test page * Fix links and update missing content * Fix links * Fix links * Fix links and collector text * Updates from Alex's feedback * Link fixes * Fix links in deploy * Fix links * More link fixes * Fix yet more links * Fix more links * Apply suggestions from code review Co-authored-by: Jack Baldry <[email protected]> * Update content/docs/tempo/next/set-up-for-tracing/setup-tempo/test/set-up-test-app.md * Update content/docs/tempo/next/set-up-for-tracing/setup-tempo/test/set-up-test-app.md * Apply suggestions from code review * Add deploy preview workflow Signed-off-by: Jack Baldry <[email protected]> * Updates for Tiffany's suggested edits * Update manifest according to PR instructions --------- Signed-off-by: Jack Baldry <[email protected]> Co-authored-by: Kim Nylander <[email protected]>
2.0 KiB
title, menuTitle, description, aliases, weight
| title | menuTitle | description | aliases | weight | |
|---|---|---|---|---|---|
| Set up Tempo | Set up Tempo | Learn how to set up a Tempo server or cluster and visualize data. |
|
300 |
Set up Tempo
To set up Tempo, you need to:
- Plan your deployment
- Deploy Tempo
- Test your installation
- (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.
Deploy Tempo
Once 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
Once Tempo is deployed, you can validate Tempo by visualizing traces data:
- Using a test application for a Tempo cluster for the Kubernetes with Tanka setup
- Using a Docker example to test the Linux setup
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 MLT example repository contains a configuration for a monolithic instance.