feat(instrumentation): Enable span streaming#629
Merged
Conversation
Bump @sentry/node 10.53.1 -> 10.59.0 and migrate from static transaction-based trace lifecycle to span streaming. Spans are now sent individually as they complete instead of being batched into a transaction at the end, enabling lower latency and per-span processing. Wrap beforeSendSpan with withStreamedSpan() and update the callback to use the streaming span shape (attributes instead of data). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Replace the beforeSendSpan callback with a single getGlobalScope().setAttributes() call after init. The global scope propagates deployment identity to every span, log, and metric without per-span mutation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Lms24
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump
@sentry/nodefrom 10.53.1 to 10.59.0 and enable span streaming(
traceLifecycle: "stream"). Spans are sent in batches as they complete instead of being emitted when the transaction finishes.The
beforeSendSpancallback that stamped deployment attributes on every spanis replaced with a single
Sentry.getGlobalScope().setAttributes()call after init.The global scope propagates deployment identity to every span, log, and metric
without per-span mutation.