You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dependency uptrace/opentelemetry-go-extra hasn't had a release for two years.
There is an official contrib package (go.opentelemetry.io/contrib/bridges/otellogrus) that is still actively maintained and kept in sync with the rest of the OTEL ecosystem.
Many of our services broke after updating all dependencies (go get -u -t ./...), because it pulled in go.opentelemetry.io/otel/log v0.22.0. Version v0.21.0 introduced a breaking change to the attributes interface, which the uptrace package never adopted, leaving it incompatible with any otel/log version from v0.21.0 and newer.
This PR replaces the uptrace bridge with the official contrib package to fix the build and avoid running into this again on future dependency updates.
mschewe
changed the title
replace unmaintained otel logrus bridge with official contrib package
Replace otel logrus bridge with official contrib package
Sep 23, 2026
btw. I think we are not using this anywhere. Maybe we should get rid of this feature entirely.
We use this to hook into the context logging in every application. Without it, our logs wouldn't have trace/span in them. It gets called in the init block of the logging package.
Can you test it by setting up a go workspace with f.ex. checkout+go-logging (your local copy), and see if the checkout logs include trace/span logs as expected?
Can you test it by setting up a go workspace with f.ex. checkout+go-logging (your local copy), and see if the checkout logs include trace/span logs as expected?
I have tested it locally and traces/spans still show up.
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
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.
The dependency
uptrace/opentelemetry-go-extrahasn't had a release for two years.There is an official contrib package (
go.opentelemetry.io/contrib/bridges/otellogrus) that is still actively maintained and kept in sync with the rest of the OTEL ecosystem.Many of our services broke after updating all dependencies (
go get -u -t ./...), because it pulled ingo.opentelemetry.io/otel/log v0.22.0. Version v0.21.0 introduced a breaking change to the attributes interface, which the uptrace package never adopted, leaving it incompatible with anyotel/logversion from v0.21.0 and newer.This PR replaces the uptrace bridge with the official contrib package to fix the build and avoid running into this again on future dependency updates.