Problem Statement
Currently, the sentry-go/otel module relies on an older version of OpenTelemetry semantic conventions (v1.12.0). The broader Go OpenTelemetry ecosystem, including popular instrumentation plugins like go-gorm/opentelemetry, has already migrated to much newer versions go-gorm/opentelemetry#41
Because of this version gap, many semantic convention key names have changed or evolved. When sentry-go/otel processes spans generated by these updated third-party plugins, it fails to correctly recognize the updated semconv keys. This mismatch causes failures in correctly binding op and leads to incomplete trace representations within Sentry.
Solution Brainstorm
Upgrade the go.opentelemetry.io/otel/semconv dependency to v1.30.0 or a newer version.
An alternative would be implementing a compatibility or mapping layer within the Sentry span processor to translate newer semconv keys back to the older v1.12.0 format.
Problem Statement
Currently, the
sentry-go/otelmodule relies on an older version of OpenTelemetry semantic conventions (v1.12.0). The broader Go OpenTelemetry ecosystem, including popular instrumentation plugins likego-gorm/opentelemetry, has already migrated to much newer versions go-gorm/opentelemetry#41Because of this version gap, many semantic convention key names have changed or evolved. When
sentry-go/otelprocesses spans generated by these updated third-party plugins, it fails to correctly recognize the updatedsemconvkeys. This mismatch causes failures in correctly bindingopand leads to incomplete trace representations within Sentry.Solution Brainstorm
Upgrade the
go.opentelemetry.io/otel/semconvdependency tov1.30.0or a newer version.An alternative would be implementing a compatibility or mapping layer within the Sentry span processor to translate newer
semconvkeys back to the older v1.12.0 format.