Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tempo] update to v2.6.0 #3310

Closed
wants to merge 1 commit into from

Conversation

portswigger-tim
Copy link

Update Tempo to version 2.6.0 in the simple tempo Helm chart.

Signed-off-by: Tim Birkett <[email protected]>
@portswigger-tim portswigger-tim changed the title [tempo] update to v2.6.0 WIP: [tempo] update to v2.6.0 Sep 13, 2024
@portswigger-tim
Copy link
Author

Doesn't quite work as expected. Investigating...

@portswigger-tim portswigger-tim changed the title WIP: [tempo] update to v2.6.0 [tempo] update to v2.6.0 Sep 13, 2024
@portswigger-tim
Copy link
Author

Seeing: failed to get trace with id: <trace-id> Status: 404 Not Found Body: since updating to 2.6.0. Refreshing a lot can occasionally get a result back so I'm guessing that blocks aren't being replicated around or something 🤷 - will ask about in the main Tempo repo or in Slack.

@Sheikh-Abubaker
Copy link
Collaborator

Seeing: failed to get trace with id: <trace-id> Status: 404 Not Found Body: since updating to 2.6.0. Refreshing a lot can occasionally get a result back so I'm guessing that blocks aren't being replicated around or something 🤷 - will ask about in the main Tempo repo or in Slack.

any updates on this ?

@portswigger-tim
Copy link
Author

I think it is as a result of the chart not setting up the querer/ingestor rings when deploying > 1 replica so instances of tempo are not aware of each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants