feat(logs): Add sentry.replay_id to logs spec
#14838
Merged
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
|
AbhiPrasad
added a commit
to getsentry/sentry-javascript
that referenced
this pull request
Sep 8, 2025
cleptric
approved these changes
Sep 10, 2025
This was referenced Sep 10, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
resolves https://linear.app/getsentry/issue/SDK-35/update-develop-docs-to-mention-sentryreplay-id-attribute
Attaching a replay id directly to logs makes it easy for users to go from log -> replay. It also vastly simplifies querying for logs in the frontend.
Right now we have only specced attaching replay to client-side logs, but in the future we can add the functionality that sdks can parse baggage to grab the
replay_idand attach the id to logs.