mirror of
https://github.com/temporalio/temporal.git
synced 2026-08-30 18:41:49 -07:00
49337f471d
## 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" />
Temporal Server docker compose files for server development
These docker compose files run Temporal server development dependencies. Basically, they run everything you need to run
Temporal server besides a server itself which you suppose to run locally on the host in your favorite IDE or as binary.
You are not supposed to use these files directly. Please use Makefile targets instead. To start dependencies:
make start-dependencies
To stop dependencies:
make stop-dependencies
See CONTRIBUTING.md for details.