feat(node): fetch breadcrumbs without tracing #14018
Open
+262
−65
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
size-limit report 📦
|
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.
This PR adds the
fetchBreadcrumbsIntegrationand enables it by default. This integration captures fetch (and undici) breadcrumbs without the need to enable tracing.Setting the
fetchBreadcrumbstop-level init option to false disables this integration. I added a top-level config option because this integration is enabled by default and we like a simple way to disable it without resorting to filtering or passing integrations.Breadcrumbs addition has been removed from
nativeNodeFetchIntegrationand itsbreadcrumbsoption has been deprecated but to preserve backwards compatibility, this property also disables the new integration. There is a test to confirm this!