Component
core/observability/tempo
A Grafana Tempo distributed-tracing server in its single-binary shape: every subsystem runs inside one process backed by a local trace store, so it renders as a single stateful server with a data volume. It receives trace spans over the OpenTelemetry protocol and other tracing wire formats, and answers trace-lookup and search queries over its HTTP API, on its own port, which a dashboards server reads to display traces. It serves its own metrics in the Prometheus format at /metrics on that HTTP port, 3200, on by default, and every Recipe publishes that address as `metrics_endpoint`. Its primary contract to consumers is the OTLP gRPC receiver: a trace producer wires to it and pushes spans there, and the component exports that receiver's host and port. It carries `observability.aggrega.ai/traces: otlp-grpc`, so an OpenTelemetry Collector's `traces` socket takes it and exports spans to that receiver. Realized on helm by two realizations the Manifest chooses between, and on compose by one. `tempo` synthesizes the server as a workload and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `tempo-chart` renders the community-maintained Tempo Helm chart, which assembles the server's configuration from named settings rather than from a hand-written file and additionally accepts spans in the Jaeger and Zipkin wire formats, so reach for it where a chart repository is reachable at build time. On compose, `tempo` runs the same image and configuration as its helm namesake, as a service publishing nothing to the host.
Herkunft
- Inhalts-Digest
- sha256:1ddd938f29ca11e02cd0bb51e457e48e9a8d4fedc43a43551025d7e2abdcb6d9
- Veröffentlicht
- 2026-11-10T10:13:15Z
- Signaturidentität
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signatur
- Offiziellapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:89434ed4833a641cb62157a4e2ec26b68383a49efa0f1d7691c3a46ca9c32df8
Referenz zu dieser Version
oci://hub.aggrega.ai/component/core/observability/tempo:1.0.0Entwicklerparameter
Werte, die der Entwickler im Aggregate festlegt.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| retention_period | string | 168h | nein | How long stored trace blocks are kept before the in-process compactor deletes them. Expressed as a Go duration (e.g. `168h` for seven days). |
Dimensionierung durch den Operator
Infrastrukturdimensionierung, die der Operator pro Umgebung anpasst.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| engine_version | string | 2.9.0 | nein | Tempo container image tag. Selects the grafana/tempo image tag the workload-synthesis realizations run, on helm and on compose; the chart-backed realization pins its own image tag. |
| source_version | string | — | nein | Version of the Helm chart the chart-backed realization pulls. Read only by that realization; the workload-synthesis realizations, on helm and on compose, pull no source artifact and ignore it. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart. |
| compute | object | — | nein | — |
| storage | object | — | nein | — |
| overrides | object (open) | — | nein | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Ausgabevertrag
Werte, die diese Komponente über die uses-Topologie an Konsumenten veröffentlicht.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| host | string | — | ja | Name the server receiving trace spans is reached at — the in-cluster Service on helm, the service name on compose. An application exporting spans points its exporter at this name together with `port`. |
| port | integer | — | ja | TCP port spans are ingested on. It carries the OpenTelemetry gRPC receiver port, not the query API port, so a consumer wires its exporter rather than its dashboard. |
| protocol | string | — | nein | How the published address is spoken to — `grpc`, so an exporter is configured for the gRPC transport rather than the HTTP one. |
| metrics_endpoint | string | — | nein | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:3200/metrics` on the HTTP API's port, which is not the published `port`. Empty where the component serves none reachable. |
uses-Sockets
Die Abhängigkeits-Sockets, über die sich diese Komponente verbindet. Das Ziel jeder über einen Socket verdrahteten Verbindung muss dessen Label-Selektor erfüllen, und jede Verbindung kann in den Slots, die der Socket deklariert, eine Anbindung tragen. Einen erforderlichen Slot muss jede Verbindung füllen, die das Aggregate oder das Release über den Socket verdrahtet.
Keine uses-Sockets deklariert.
Anbindungs-Slots
Benannte Bindungspunkte, an denen ein Feature an diese Komponente angebunden wird. Der Selektor eines Slots schränkt ein, welches Feature ihn füllen darf, und seine inject-Liste benennt, wie das Feature sein Material liefern darf. Ein erforderlicher Slot muss auf jeder Instanz gebunden sein, durch eine Anbindung an der Instanz oder in einem darüberliegenden Geltungsbereich, und ein sensibler Slot ist für den Umgang mit geheimem Material deklariert. Ein Feature kann auch unter einem Namen angebunden werden, den kein Slot deklariert.
Keine Anbindungs-Slots deklariert.
Zulassungsliste für Selbstinjektion
env
Beziehungen
Typisierte Kanten zu und von anderen veröffentlichten Entitäten. Eine Referenz ohne veröffentlichtes Ziel wird als unterbrochene Kante statt als Link dargestellt.
Verwendet
Diese Entität verwendet nichts aus dem Katalog.
Verwendet von
verwendet Socket «backend»
verwendet Socket «databases»
verwendet Socket «etcd»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «forward_target»
verwendet Socket «traces»
verwendet Socket «scrape_target»
verwendet Socket «backend»
verwendet Socket «database»
gilt für
gilt für
gilt für
implementiert
implementiert
implementiert