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
It was discovered during refactor from go.uber.org/atomic to sync/atomic that the former is still a part of the dependencies. These are derived indirectly from the jaeger module in the tracer package.
From the official documentation, it is announced that jaeger tracer is being deprecated in favour of OpenTelemetry SDKs and therefore we have to deprecate and remove it from here as well. This will not only remove the deprecated tracer but also the outdated dependency on go.uber.org/atomic completely.
As we decide upon a deprecation strategy for this, this issue can be assigned to me and I'll work on it.
The text was updated successfully, but these errors were encountered:
I think this issue is too specific to one tracer. Basically right now all our tracers are "deprecated in favor of opentelemetry".
We also have #2345 which outlines how to go forward and let users a time to migrate from tracers to opentelemetry.
It was discovered during refactor from
go.uber.org/atomic
tosync/atomic
that the former is still a part of the dependencies. These are derived indirectly from thejaeger
module in the tracer package.From the official documentation, it is announced that
jaeger
tracer is being deprecated in favour of OpenTelemetry SDKs and therefore we have to deprecate and remove it from here as well. This will not only remove the deprecated tracer but also the outdated dependency ongo.uber.org/atomic
completely.As we decide upon a deprecation strategy for this, this issue can be assigned to me and I'll work on it.
The text was updated successfully, but these errors were encountered: