fix(attributes): Add deprecated sentry.thread.id - #451
Merged
Conversation
mjq
requested review from
a team,
Lms24,
cleptric and
nsdeschenes
as code owners
June 23, 2026 14:27
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Attributes
Other
Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧Deps
Other
Other
🤖 This preview updates automatically when you update the PR. |
cleptric
approved these changes
Jun 23, 2026
4 tasks
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.
Transaction-based spans wrote the current thread ID into
sentry.thread.id. The Sentry backend aliases this tothread.id.Span streaming SDKs are correctly using our conventional
thread.iddirectly, but the backend can't see them due to that existing alias.Add a deprecated
sentry.thread.idpointing tothread.idas its replacement. Once this is merged and updated in Snuba, coalescing will make this start working on the Sentry side. We should then be able to remove Sentry's custom mapping, relying on the definition here instead.See DAIN-1733.