make SplunkPostDocLoadResourceInstrumentation aware of upstream context (#357) #398
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.
maintaining a mapping of the source URLs of those elements to the span context when they were inserted
context as the logic that initiates the resource load
Description
Problem: when a resourceFetch span is created by the SplunkPostDocLoadResourceInstrumentation, context is not propagated from the code that initiated the resource load.
Solution: use a mutation observer to detect when new elements are added to the document head and record the tracing context at that time, to be used later when resourceFetch spans are created.
Fixes #357
Type of change
How has this been tested?
Checklist: