Tempo
Purpose: For platform engineers, operators, SREs, documents the Tempo service in openCenter-gitops-base.
tempo is the distributed tracing backend in the observability stack. In this repository it is deployed as a Helm release in observability and is typically fed by OpenTelemetry collectors over OTLP.
What This Repo Deploys
-
HelmRelease/tempo -
Base values from the service
helm-values/directory -
Optional
tempo-values-override
When to Use It
-
You need central distributed trace storage.
-
You want OTLP-native trace ingestion.
-
You want Grafana and TraceQL-based query workflows.
Key Integration Points
-
OpenTelemetry collectors export traces to Tempo.
-
Grafana queries Tempo for trace views and correlations.
-
Object storage configuration is a major cluster-specific concern.
Configuration Surfaces
-
Service path:
applications/base/services/observability/tempo/ -
Namespace:
observability -
Flux object:
HelmRelease/tempo -
Base values Secret:
tempo-values-base -
Override values Secret:
tempo-values-override