New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(browser): Send standalone fetch and XHR spans if there's no active parent span #11783
Merged
Conversation
This file contains 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
Lms24
changed the base branch from
develop
to
lms/feat-core-span-envelope-trace-header
April 25, 2024 11:03
size-limit report 📦
|
mydea
approved these changes
Apr 25, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very nice!
Lms24
force-pushed
the
lms/feat-core-span-envelope-trace-header
branch
from
April 25, 2024 14:46
47a67db
to
5095e82
Compare
Base automatically changed from
lms/feat-core-span-envelope-trace-header
to
develop
April 25, 2024 15:19
Lms24
force-pushed
the
lms/feat-browser-http-client-standalone-spans
branch
from
April 25, 2024 15:30
0a9e935
to
78f1279
Compare
Lms24
added a commit
that referenced
this pull request
May 10, 2024
…rent span (#11974) We introduced sending standalone `http.client` spans in #11783. Subsequently, we had to revert this change due to internal timeline problems (😢). However, in the revert PR (#11879) we missed that originally, we checked for an active parent span and only then created an `http.client` span. The result were `http.client` _transactions_ which we also don't want. This patch fixes that by re-introducing the `hasParent` check as it was pre-#11783.
andreiborza
pushed a commit
that referenced
this pull request
May 16, 2024
…rent span (#11974) We introduced sending standalone `http.client` spans in #11783. Subsequently, we had to revert this change due to internal timeline problems (😢). However, in the revert PR (#11879) we missed that originally, we checked for an active parent span and only then created an `http.client` span. The result were `http.client` _transactions_ which we also don't want. This patch fixes that by re-introducing the `hasParent` check as it was pre-#11783.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Builds on top of #11696 and #11699
This PR enables sending standalone
http.client
spans for outgoingfetch
and XHR requests if there's no active parent span. These spans will belong to the same trace id as a potentially previously started pageload or navigation span.Adjusted integration tests to test the newly sent spans and their trace lifetime.
ref #11562