Expected Behavior
If you follow the steps in https://github.com/temporalio/temporal/blob/main/docs/development/tracing.md, you can run Temporal locally and collect tracing information.
Actual Behavior
No traces are visible within Graphana. It appears to be from the Tempo container failing on startup, with the following error:
don't actually see any traces in Graphana. It appears to be because the Graphana Tempo container fails on start-up, with the following error:
2026-04-23 15:20:27.777 | failed parsing config: failed to parse configFile /etc/tempo.yaml: yaml: unmarshal errors:
2026-04-23 15:20:27.777 | line 47: field ingester not found in type app.Config
2026-04-23 15:20:27.777 | line 50: field compactor not found in type app.Config
2026-04-23 15:20:27.777 | line 64: field traces_storage not found in type generator.Config
2026-04-23 15:20:27.777 | line 67: field local_blocks not found in type generator.ProcessorConfig
This looks like it was just some breaking change in the config file format that Tempo is loading. And it's just a matter of updating whatever settings we have checked into the repo.
Expected Behavior
If you follow the steps in https://github.com/temporalio/temporal/blob/main/docs/development/tracing.md, you can run Temporal locally and collect tracing information.
Actual Behavior
No traces are visible within Graphana. It appears to be from the Tempo container failing on startup, with the following error:
don't actually see any traces in Graphana. It appears to be because the Graphana Tempo container fails on start-up, with the following error:
This looks like it was just some breaking change in the config file format that Tempo is loading. And it's just a matter of updating whatever settings we have checked into the repo.