Files
temporal/develop/docker-compose/grafana/provisioning/tempo/tempo.yaml
Chris Smith 49337f471d Update Graphana Tempo config for latest version (#10055)
## What changed?

Updates the Graphana Tempo configuration used for the service when
running locally. (Simply copying a more recent version of the
single-binary setup.)

Fixes #10053.

## Why?

Previously, the Tempo container would fail on startup. Preventing any
collection of OTel traces. It appeared to stem from breaking changes in
the Tempo service itself, as it modified the schema of its configuration
file.

I'll admit I am out of my depth here. But some of the field changes are
called out in their upgrade guide here:

https://grafana.com/docs/tempo/latest/set-up-for-tracing/setup-tempo/upgrade/

## How did you test it?
- [x] built
- [x] run locally and tested manually
- [ ] ~covered by existing tests~ - NA?
- [ ] ~added new unit test(s)~ - NA?
- [ ] ~added new functional test(s)~ - NA?

I ran the
https://github.com/temporalio/samples-go/tree/main/opentelemetry sample,
and within the Graphana UI on http://localhost:3000/ I saw data showing
up.

<img width="1244" height="620" alt="image"
src="https://github.com/user-attachments/assets/320642a8-1b91-4428-bb6d-1f2b090016b8"
/>
2026-04-24 19:09:59 -07:00

49 lines
960 B
YAML

# Copied from https://github.com/grafana/tempo/blob/main/example/docker-compose/single-binary/tempo.yaml
stream_over_http_enabled: true
server:
http_listen_port: 3200
log_level: info
distributor:
receivers:
otlp:
protocols:
grpc:
endpoint: "tempo:4317"
http:
endpoint: "tempo:4318"
metrics_generator:
registry:
external_labels:
source: tempo
cluster: docker-compose
storage:
path: /var/tempo/generator/wal
remote_write:
- url: http://prometheus:9090/api/v1/write
send_exemplars: true
query_frontend:
mcp_server:
enabled: true
storage:
trace:
backend: local
wal:
path: /var/tempo/wal # where to store the wal locally
local:
path: /var/tempo/blocks
overrides:
defaults:
metrics_generator:
processors: ["span-metrics", "service-graphs"]
generate_native_histograms: both
usage_report:
reporting_enabled: false