Tempo Coordinator K8S

  • Canonical Observability
Channel Revision Published Runs on
latest/edge 37 Yesterday
Ubuntu 22.04
juju deploy tempo-coordinator-k8s --channel edge
Show information

Platform:

Tempo Coordinator Charm (part of Charmed Tempo HA)

tempo-coordinator-k8s is a charm that, in conjunction with the tempo-worker-k8s charm, deploys and operates Tempo, a distributed tracing backend by Grafana.

This charm, together with one or multiple worker charms, handles deployment, scaling, configuration, and Day 2 operations specific to Tempo.

This operator is the main entry point to the distributed Tempo deployment. It is responsible for configuring the worker nodes and runs an Nginx instance to provide an unified access point to all incoming traffic.

Important! This charm only works in conjunction with its counterpart, and, when deployed in isolation, is not functional. This documentation only contains charm-specific, and as such relatively low-level documentation. For the solution-level documentation, look at the solution-level Charmed Tempo HA docs.

The charm imposes configurable resource limits on the workload, can be readily integrated with trace providers, and comes with built-in alert rules and dashboards for self-monitoring.

This charm is:

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 prometheus is part of the Canonical Observability Stack. It is an open source project that warmly welcomes community projects, contributions, suggestions, fixes and constructive feedback.

Thinking about using the Canonical Observability Stack for your next project? Get in touch!


Help improve this document in the forum (guidelines). Last updated 2 months ago.