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
In PR #2342 we are providing a observability provider friendly tracing provider to deprecate the current X-Ray specific provider tracing.base.baseprovider and tracing.base.BaseSegment. This new provider solution will enable our customer to send traces to Third party observability provider with ease. After #2342 is merged, the current provider will no longer be used in Tracer.
Which area does this relate to?
Tracer
Solution
This Deprecation is straightforward. This provider class is mostly for internal purpose and X-ray only. If there are customers developing their own provider based on this base provider, they will be able to migrate to the new provider proposed in #2342 with few method/class name changes
Why is this needed?
In PR #2342 we are providing a observability provider friendly tracing provider to deprecate the current X-Ray specific provider
tracing.base.baseprovider
andtracing.base.BaseSegment
. This new provider solution will enable our customer to send traces to Third party observability provider with ease. After #2342 is merged, the current provider will no longer be used in Tracer.Which area does this relate to?
Tracer
Solution
This Deprecation is straightforward. This provider class is mostly for internal purpose and X-ray only. If there are customers developing their own provider based on this base provider, they will be able to migrate to the new provider proposed in #2342 with few method/class name changes
Acknowledgment
The text was updated successfully, but these errors were encountered: