Update Graphana Tempo config for latest version#10055
Merged
Conversation
|
|
chrsmith
force-pushed
the
chrsmith/update-tempo-config
branch
from
480fc71 to
d6613a4
Compare
stephanos
approved these changes
Apr 24, 2026
Contributor
stephanos
left a comment
stephanos
left a comment
There was a problem hiding this comment.
Can we also change the docker compose to pin the tempo version? we shouldn't be using latest there.
Contributor
Author
That's a good point. I'm inclined to just merge this as-is, and futs with pinning some of the dependent services when I'm a bit more confident in knowing what I'm doing 😅 . But yeah, I agree that some sort of "always use specific versions" + some semi-regular chore to update things is preferable to it just randomly breaking like this from time to time. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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?
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.