feat: Allow Hybrid SDK to setTrace

[bitsandfoxes]

Resolves #3562
Follows #4188

Depends on sentry-native release: getsentry/sentry-native#1137
Corresponding PR on Unity: getsentry/sentry-unity#1997

Context

Native events and crashes do not share the same trace ID as the rest of the layers. This is relevant in two ways:

1. Synching the trace for native events
2. Allowing hybrid SDKs (i.e. RN, Unity) to propagate their trace to Java - and implicitly to native

Changes

Setting the trace from hybrid SDKs

The Java SDK provides an API to allow hybrid SDKs to set a trace outside of accepting trace-header & baggage. This is done in the InternalSentrySdk. It accepts a trace ID, the parent span ID, and optionally a sample rate, and a sample rand. Assuming that enableTraceIdGeneration and performance is disabled, writing these to the propagation context allows the SDK to effectively "continue the trace".

Synching trace to native

The NDKScopeObserver is already getting invoked on changes to the propagation context via setTrace. The changes in getsentry/sentry-native#1137 provide a way to set the Trace context on the native scope.

Result

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against e6a7438

[krystofwoldrich]

In JS the spanId is now called propagationSpanId but it's the same thing with different names.

https://github.com/getsentry/sentry-javascript/blob/95cc948ef0136e1228916e3216c4a08b84fa8230/packages/core/src/types-hoist/tracing.ts#L45

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[adinauer]

Left some thoughts after giving this a quick look

[adinauer]

Can we add an optional Baggage param here as well?
I would assume we want to sync that between the SDKs as well.

[bitsandfoxes]

I don't see the need or benefit of doing that from the Unity SDK's perspective. @krystofwoldrich would this help RN?

[krystofwoldrich]

At the moment, I don't see why we would need Baggage synced as well.

[bruno-garcia]

I believe we pass replayId via baggage to downstream services
Might need that on React Native (which has Replay)

[krystofwoldrich]

We don't need that because the ReplayID is generated on native and synced up to RN Replay Integration which adds it to DSC.

https://github.com/getsentry/sentry-react-native/blob/5dff5ee95fb4c3d8f2589b80d4d355fecde17778/packages/core/src/js/replay/mobilereplay.ts#L107

The traceID is the opposite, hybrid (RN) generates it and we need to sync it down to native.

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	385.00 ms	422.86 ms	37.86 ms
Size	1.58 MiB	2.21 MiB	642.02 KiB

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[adinauer]

LGTM

[markushi]

LGTM!