docs(replay): Add traces_by_timestamp field to replay event spec#16602
Draft
docs(replay): Add traces_by_timestamp field to replay event spec#16602
traces_by_timestamp field to replay event spec#16602Conversation
Document the new `traces_by_timestamp` field added in getsentry/sentry-javascript#18048. This field provides timestamped trace associations as `[timestamp, trace_id]` pairs, enabling Sentry to correlate replay events with the correct trace by temporal ordering. The existing `trace_ids` field is preserved for backwards compatibility. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
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
1 participant
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.
DESCRIBE YOUR PR
Document the new
traces_by_timestampfield added to the replay event payload in getsentry/sentry-javascript#18048.This field sends
[timestamp, trace_id]pairs alongside the existingtrace_idslist, enabling Sentry to associate replay custom events with the correct trace using temporal ordering (needed for migrating custom rrweb events to EAP).traces_by_timestampto the Replay Attributes table (typeList[[Number, String]], optional, since 1.3.0)trace_idsdescription for clarityIS YOUR CHANGE URGENT?
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Co-Authored-By: Claude noreply@anthropic.com