feat(develop/spans): Add Span Buffer specification #16327
+77
−26
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
buenaflor
reviewed
Feb 10, 2026
Contributor
buenaflor
left a comment
buenaflor
left a comment
There was a problem hiding this comment.
overall looks reasonable, however what is the long-term plan for the span buffer page? I'd imagine that it will easily gets out of sync with the telemetry processor docs and since both kinda have the same info it could be confusing which one is the source of truth for spans
Member
|
The work on the telemetry processor is on hold. So having all things spans under one menu item is ok imo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
As discussed yesterday, this PR adds a spec for a span buffer. This is less specified than the Telemetry Processor but more formal than the recommendation in the Span-First implementation guide (which I removed in favor of this page).
Most important change: We added weight-based flushing as an addition to the previous flushing behaviour
closes https://linear.app/getsentry/issue/FE-718/span-buffer-section-in-dev-docs