Manoel Aranda Neto
Manoel Aranda Neto
that makes total sense, I just wanted to be sure that the important bits are correct which is: ``` final SentryTraceHeader sentryTraceHeader = activeSpan.toSentryTrace(); request.getHeaders().add(sentryTraceHeader.getName(), sentryTraceHeader.getValue()); ```
@crummy indeed, thanks for reporting this, subscribe to this issue please https://github.com/getsentry/sentry-java/issues/1346
@lobsterkatie mind reviewing https://github.com/getsentry/sentry-docs/pull/3324 ? we've got questions from multiple people already so we need to tackle this at least for the Java SDK
@Olegt0rr it's the PR's title, `sentry-trace`
Keeping it open as a placeholder for other platforms, it's still not documented for the other SDKs other than Java/Android afaik.
This should be common content and just the code snippet would change per platform, only relevant for server-side SDKs. Java is already done but should adapt to the common content.
The downside of it is that if people copy-paste that, everything would be disabled by default. That was the idea behind adding the default values.
@armcknight I've added the min. required scope to this [page](https://docs.sentry.io/product/cli/dif/#permissions) a while ago.
Option 1 is a good first step. Option 2 wouldn't work because we pre-compile with the min. supported version and ship it as a dependency of the Sentry Android SDK....
Yeah, this is something I looked into in the past as well. https://github.com/marandaneto/android-exit-reasons-api-sample But it was just a preview (Android 11), I guess we can start considering it. Thanks @supervacuus...