user.segment isn't unified.
iOS reads from user.data and Java from user.other.
#37 but the right behavior is adding a top-level property called segment.
https://github.com/getsentry/sentry-javascript/blob/beb3c973c0f10c538c8369983fc08c5bd031bfde/packages/types/src/user.ts#L8
Java issue
tracePropagationTargets isn't unified, but we'd need to offer at least one option.
Java reads from tracingOrigins and iOS does not have it at all.
#39
baggage behavior isn't unified.
Java always overwrites the baggage header which is wrong per spec, iOS does not.
https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/#baggage
Java has an open draft that addresses that.
traceSampling SDK option.
Java is guarded by this option, iOS does not have it at all, not sure if such a flag should exist.
Apparently, it's only gated by tracePropagationTargets, we don't need such traceSampling flag.
Java issue
SDK's don't implement the dynamic_sampling_context_frozen logic, do we need it?
https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/#unified-propagation-mechanism
https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/#freezing-dynamic-sampling-context
Java has an open draft that addresses that.
This is experimental and we should not do anything for now, even less relevant for Mobile.
How do we track the adoption of DS on SDKs? do we need to?
Remove isTraceSampling option so we can propagate baggage by default
Related issues
user.segmentisn't unified.iOS reads from
user.dataand Java fromuser.other.#37 but the right behavior is adding a top-level property called
segment.https://github.com/getsentry/sentry-javascript/blob/beb3c973c0f10c538c8369983fc08c5bd031bfde/packages/types/src/user.ts#L8
Java issue
iOS issue
Docs PR
tracePropagationTargetsisn't unified, but we'd need to offer at least one option.Java reads from
tracingOriginsand iOS does not have it at all.#39
baggagebehavior isn't unified.Java always overwrites the
baggageheader which is wrong per spec, iOS does not.https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/#baggage
Java has an open draft that addresses that.
traceSamplingSDK option.Java is guarded by this option, iOS does not have it at all, not sure if such a flag should exist.
Apparently, it's only gated by
tracePropagationTargets, we don't need suchtraceSamplingflag.Java issue
traceSamplingflag in favor oftracePropagationTargetssentry-java#2244iOS will do
tracePropagationTargets#39SDK's don't implement the
dynamic_sampling_context_frozenlogic, do we need it?https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/#unified-propagation-mechanism
https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/#freezing-dynamic-sampling-context
Java has an open draft that addresses that.
This is experimental and we should not do anything for now, even less relevant for Mobile.
How do we track the adoption of DS on SDKs? do we need to?
Remove
isTraceSamplingoption so we can propagate baggage by defaultRelated issues