Conversation
DrJosh9000
approved these changes
Apr 29, 2026
Contributor
DrJosh9000
left a comment
There was a problem hiding this comment.
Ooooh, good riddance!
167b580 to
35f0cd4
Compare
2 tasks
DrJosh9000
pushed a commit
that referenced
this pull request
May 4, 2026
Rip out opentracing tracing backend
2 tasks
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
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.
Description
Opentracing was deprecated even when we added opentelemetry. We should get rid of it, but we haven't been able to make breaking changes. We're doing v4 now! Goodbye, opentracing 🫡
Changes
Remove the
opentracingtracing backend. Onlyopentelemetrywill be a permitted tracing backend now.Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go tool gofumpt -extra -w .)Disclosures / Credits
This one was mostly Amp.