Why sentry ktor client plugin always binds to a transaction in android? #4776

Hi @AngryGami, you're right to say that what you're trying to do doesn't work as you would expect.

In Android, we use something called global hub (aka scopes, with the hub -> scopes migration) mode.
This means that there's only a single set of scopes (hence, a single transaction and span) active at a given point in time, that are shared between threads.
This is in contrast with the behavior we have on JVM, where global hub mode is disabled by default, and each thread gets their own independent stack of scopes.
The reason we have these 2 modes is that, for Android, the thread local isolation doesn't really fit, as it's common to have operations that jump between threads.

With the way the auto-instrumentation is structured and our use of global hub mode, you get a correct span timeline, even though the hierarchy might be incorrect.
If we were to attach to the span though, instead of the transaction, the hierarchy would be completely broken, as you would grab whatever span happens to be active on the global hub (scopes) at the moment you create the child span for the HTTP request.

It should still be possible to do what you want, but at the moment it requires using APIs marked as internal. For example, you could create a new transaction using Sentry.startTransaction(transactionContext), constructing the transactionContext in a way that the transaction you start becomes a child of the current one. Then, set the currently started transaction as the active one on the scope, and at the end of the process restore the old one.

As you can understand this is not great currently, and requires a lot of manual work.
We're looking to improve this in future versions of the SDK, also considering that we're planning to move to a spans only API which will allow us to get rid of transactions, hopefully simplifying things.

I hope this helps.

Hi @lcian
Thanks for thorough reply :)
As far as I understand (and from my experience), at least in modern Android+Kotlin development - main reason why operations might jump from thread to thread is usage of coroutines. SentryContext handles this (if used carefully) with almost no issues. Span that is returned by Sentry.getSpan() is like 90% of the time one that I'm expecting to see (other 10% are most likely my mistakes) so having at least an option to tell plugin to use it instead would be nice.