Skip to content

Event processor migration: Browser fetch timestamp adjustments (TBD) #20376

Closed
#20778
Closed
Event processor migration: Browser fetch timestamp adjustments (TBD)#20376
#20778
Assignees
nicohrubec

Description

@Lms24
Lms24
opened on Apr 17, 2026

This is a tough one: It seems like we update span timestamps based on corrected timestamps for streamed fetch requests which are stored in a map. The logic itself is easy to port to client.on('processSpan') but the question is rather, if the map is populated as previously once the span ended. Given our span capturing and enqueuing logic is sync, and once enqueued we can't mutate spans anymore, this might be a timing issue we can't solve correctly.

Activity

  1. linear-code commented on Apr 17, 2026

    @linear-code
    linear-codeBot
    on Apr 17, 2026 – with Linear Code

    JS-2213

  2. nicohrubec
    self-assigned this
    on May 9, 2026
  3. nicohrubec
    added a commit that references this issue on May 9, 2026

    feat(browser): Defer fetch span end for streamed responses

    745a2f3
  4. nicohrubec
    closed this as completedin #20778on May 15, 2026
  5. nicohrubec
    added a commit that references this issue on May 15, 2026

    feat(browser): Add `fetchStreamPerformanceIntegration` for streamed r…

    46385f0

  6. github-actions commented on May 26, 2026

    @github-actions
    github-actionsBot
    on May 26, 2026 – with GitHub Actions
    Contributor

    A PR closing this issue has just been released 🚀

    This issue was referenced by PR #20778, which was included in the 10.54.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions