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]>
1.5 KiB
title, menuTitle, description, aliases, weight
| title | menuTitle | description | aliases | weight |
|---|---|---|---|---|
| Plan your Tempo deployment | Plan your deployment | Plan your Grafana Tempo deployment | 200 |
Plan your Tempo deployment
To plan your Grafana Tempo deployment, you should:
-
Identify your use case Decide what you need from Tempo. For example, consider if you want a basic installation, horizontal scalability, multi-tenancy, or advanced data storage. Your use case determines the deployment architecture and resource requirements.
-
Estimate tracing data volume Assess the amount of tracing data your environment will generate. This helps you size your cluster and storage. Refer to the Size your cluster section for guidance on calculating storage and performance needs.
-
Choose a deployment mode. Tempo supports monolithic and microservices deployment modes.
- Use the monolithic mode for simple, single-tenant environments or smaller workloads.
- Use the microservices mode for large-scale, multi-tenant, or highly available deployments. Review the Deployment modes documentation to compare options and select the best fit for your use case.
By following these recommendations, you can plan a Tempo deployment that matches your operational requirements and scales with your tracing data.
Next steps
Once you've planned your deployment, you can Deploy your Tempo instance using the deployment mode you selected.