fix: isolate mediaDevices traces #1779
Merged
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.
💡 Overview
Continuation of #1765.
mediaDevice
traces were tracked in a single sharedTracer
instance.While this is ok for the majority of the integrations, this can be problematic for customers allowing one to be connected to two separate
call
instances from a single browser tab.This PR scopes the traces to the
call
instance.📝 Implementation notes
tracer
instance in the lowest level APIsgetUserMedia
invocations triggered outside of our SDK anymorecreate
trace - we include the SFU name in it now🎫 Ticket: https://linear.app/stream/issue/REACT-365/rtc-tracing-and-performance-stats-tracking