Joe Elliottandzeekay
618c8c8a06
* remove deprecated modes Signed-off-by: Joe Elliott <[email protected]> * consolidate alloy and local storage Signed-off-by: Joe Elliott <[email protected]> * distributed example Signed-off-by: Joe Elliott <[email protected]> * consolidated the vulture example into single-binary Signed-off-by: Joe Elliott <[email protected]> * compactor => scheduler/worker Signed-off-by: Joe Elliott <[email protected]> * debug! Signed-off-by: Joe Elliott <[email protected]> * multi-tenant Signed-off-by: Joe Elliott <[email protected]> * otel collector -> multitenant Signed-off-by: Joe Elliott <[email protected]> * fork all shared Signed-off-by: Joe Elliott <[email protected]> * readmes Signed-off-by: Joe Elliott <[email protected]> * enable mcp Signed-off-by: Joe Elliott <[email protected]> * clean up compose references Signed-off-by: Joe Elliott <[email protected]> * restore local readme Signed-off-by: Joe Elliott <[email protected]> * Add vulture to all examples Signed-off-by: Joe Elliott <[email protected]> * prometheus config Signed-off-by: Joe Elliott <[email protected]> --------- Signed-off-by: Joe Elliott <[email protected]>
2.4 KiB
title, menuTitle, description, weight, aliases
| title | menuTitle | description | weight | aliases | |||
|---|---|---|---|---|---|---|---|
| Deploy Tempo | Deploy your Tempo instance | Deploy Grafana Tempo for your tracing needs. | 300 |
|
Deploy Tempo
Tempo can be easily deployed through a number of tools, including Helm, Tanka, Kubernetes, and Docker.
The following procedures provide example Tempo deployments that you can use as a starting point.
Tempo can be deployed in a number of ways, depending on your needs and environment. You can deploy Tempo in a monolithic mode or in a microservices mode.
You can also use Docker to deploy Tempo using the Docker examples.
{{< admonition type="note" >}} Grafana Tempo does not come with any included authentication layer. You must run an authenticating reverse proxy in front of your services to prevent unauthorized access to Tempo (for example, nginx). Manage authentication for more details {{< /admonition >}}
Deploy locally
Monolithic mode (single binary) is commonly used for a local installation, testing, or small-scale deployments. This mode can be deployed using a pre-compiled binary, OS-specific packaging, or Docker image. While it's possible to deploy monolithic mode in a Kubernetes cluster, it is not recommended for production use.
Check out the Docker examples for more information.
Deploy using Kubernetes
Kubernetes deployment examples:
- Deploy with Helm (microservices and monolithic)
- Deploy with Tempo Operator (microservices)
- Deploy on Kubernetes using Tanka (microservices)
{{< admonition type="note" >}} The Tanka and Helm examples are equivalent. They are both provided for people who prefer different configuration mechanisms. {{< /admonition >}}
For more information, refer to Deploy Tempo on Kubernetes.