Charmed Tempo HA is a solution that handles deployment, scaling, and Day 2 operations specific to Tempo, a distributed tracing backend by Grafana Labs.
The solution consists of two charms which have distinct responsibilities:
tempo-coordinator-k8s
: ingress, cluster coordination, single integration facadetempo-worker-k8s
: run one or more tempo application components
Together, these two charms drive the Tempo application, and can be composed with other operators to deliver a complex application or service. In particular, you can integrate the coordinator charm with the cos-lite stack to add distributed tracing to your observability toolkit.
Tempo allows efficient storage and querying of distributed traces for all of your charmed applications. It can be readily integrated with tracing sources with support for common open source tracing protocols, including Jaeger
, Zipkin
, and OpenTelemetry
.
This solution is:
- intended to be used together with
grafana-k8s
. - intended to be used with other charms that will push their traces into it for storage and querying.
In this documentation
Tutorial Get started - a hands-on introduction for new users deploying the charmed operator. |
How-to guides Step-by-step guides covering key operations and common tasks |
Explanation Concepts - discussion and clarification of key topics |
Reference Technical information - specifications, APIs, architecture |
Project and community
Charmed Tempo is part of the Canonical Observability Stack. It’s an open source project that warmly welcomes community projects, contributions, suggestions, fixes and constructive feedback.
- Read our Code of conduct
- Join the Discourse community forum
- Join the Matrix community chat
- Contribute on GitHub
Thinking about using the Canonical Observability Stack for your next project? Get in touch!