test(node): Add integration test to demonstrate sample rate propagation of incoming trace #14788
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.
While investigating an internally reported SDK issue, I had the suspicion that our Node SDK might handle the sample rate from an incoming
baggageheader incorrectly. Turns out that's not the case and things work correctly. I couldn't find a test though, where we specifically cover a non1.0sentry-sample_ratebaggage value, so I figured there's value in adding this test.