getsentry uses the same SDK as Sentry. However, they are technically two different deployments and we cannot guarantee that they'll be deployed in lockstep.
To eliminate any dependencies on merge/deploy order, getsentry needs to work with both span streaming and legacy SDK modes.
Add a shim (or rather extend the existing one) to getsentry that uses either legacy or span streaming API based on whether span streaming is enabled. This needs to cover all tracing API usage in getsentry, including but not limited to start_transaction, start_span, span.set_data, @trace…
This can be merged before the main Sentry dogfooding branch.
getsentry uses the same SDK as Sentry. However, they are technically two different deployments and we cannot guarantee that they'll be deployed in lockstep.
To eliminate any dependencies on merge/deploy order, getsentry needs to work with both span streaming and legacy SDK modes.
Add a shim (or rather extend the existing one) to getsentry that uses either legacy or span streaming API based on whether span streaming is enabled. This needs to cover all tracing API usage in getsentry, including but not limited to
start_transaction,start_span,span.set_data,@trace…This can be merged before the main Sentry dogfooding branch.