docs: Highlight that scope tags are not applied to streamed spans - #23904
Open
chargome wants to merge 1 commit into
Open
docs: Highlight that scope tags are not applied to streamed spans#23904chargome wants to merge 1 commit into
chargome wants to merge 1 commit into
Conversation
The v11 migration guide only mentioned this in a trailing note inside the `beforeSendTransaction` section, where users who never used that option would not look. Give it its own subsection with before/after examples, since it silently affects every app that enriches transactions with tags. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Hyk7rMtFEFUgLnS5YYekxJ
chargome
marked this pull request as ready for review
September 2, 2026 08:44
chargome
enabled auto-merge (squash)
September 2, 2026 09:51
andreiborza
reviewed
Sep 2, 2026
| #### Scope `tags` and `extra` are not applied to spans | ||
|
|
||
| Streamed spans only carry attributes, so scope `tags` and `extra` (set via `Sentry.setTag(s)`, `Sentry.setExtra(s)` or the equivalent scope methods) are no longer applied to spans. | ||
| This affects every span, including the segment span that replaced the transaction, and the SDK does not warn about it: the data is simply missing from your spans. |
Member
There was a problem hiding this comment.
Suggested change
| This affects every span, including the segment span that replaced the transaction, and the SDK does not warn about it: the data is simply missing from your spans. | |
| This affects every span, including the segment span that replaced the transaction. |
l: Seems over the top/not needed
| Streamed spans only carry attributes, so scope `tags` and `extra` (set via `Sentry.setTag(s)`, `Sentry.setExtra(s)` or the equivalent scope methods) are no longer applied to spans. | ||
| This affects every span, including the segment span that replaced the transaction, and the SDK does not warn about it: the data is simply missing from your spans. | ||
|
|
||
| Tags and extra still apply to errors, so you don't have to remove them. |
Member
There was a problem hiding this comment.
l: Could we add an example for what is ok to keep?
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.
Hoists the "scope
tagsandextraare not applied to streamed spans" note out of thebeforeSendTransactionsection into its own subsection of the v11 span streaming migration guide, withsetTag(s)→setAttribute(s)examples, since the behaviour affects everyone and fails silently.