ref: Use span tree to send transaction events

[lforst]

No description provided.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser	22.22 KB (0%)
@sentry/browser (incl. Tracing)	33.31 KB (0%)
@sentry/browser (incl. Tracing, Replay)	69.09 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	62.42 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	73.15 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	85.34 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	87.21 KB (0%)
@sentry/browser (incl. metrics)	26.5 KB (0%)
@sentry/browser (incl. Feedback)	38.45 KB (0%)
@sentry/browser (incl. sendFeedback)	26.85 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.45 KB (0%)
@sentry/react	24.97 KB (0%)
@sentry/react (incl. Tracing)	36.36 KB (0%)
@sentry/vue	26.33 KB (0%)
@sentry/vue (incl. Tracing)	35.17 KB (0%)
@sentry/svelte	22.36 KB (0%)
CDN Bundle	23.42 KB (0%)
CDN Bundle (incl. Tracing)	35.05 KB (0%)
CDN Bundle (incl. Tracing, Replay)	69.18 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	74.38 KB (0%)
CDN Bundle - uncompressed	68.8 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	103.66 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	214.13 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	226.79 KB (0%)
@sentry/nextjs (client)	36.24 KB (0%)
@sentry/sveltekit (client)	33.95 KB (0%)
@sentry/node	112.43 KB (-0.5% 🔽)
@sentry/node - without tracing	89.92 KB (-0.54% 🔽)
@sentry/aws-serverless	98.94 KB (-0.55% 🔽)

[lforst]

For posterity:

Our Prisma integration tests made me realize, why this probably cannot work. Prisma does two things in their tracing implementation that deviate from the happy path:

• They start spans with a "virtual" parent, meaning that they start spans before they start a parent.
• They append spans to already finished parents.

Both of these cases mean that we would need to buffer spans in our span processor which is exactly what we would like to avoid.