ref(node): Cache undici trace propagation decisions - #8136
Merged
Conversation
AbhiPrasad
requested review from
a team,
Lms24 and
stephanie-anderson
and removed request for
a team
May 16, 2023 15:33
Lms24
approved these changes
May 16, 2023
Contributor
size-limit report 📦
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Similar to how the http integration works for Node, add a LRUMap that caches span creation/trace propagation decisions so we don't have to recompute expensive regex.
See: #8130 for some more context.
This was done as a quick win for an ask on slack: https://sentry.slack.com/archives/C28MX5WAJ/p1684250464132119?thread_ts=1684166405.392469&cid=C28MX5WAJ