feat(browser): Add interactionsSampleRate to browserTracingIntegration options#12023
Merged
feat(browser): Add interactionsSampleRate to browserTracingIntegration options#12023
interactionsSampleRate to browserTracingIntegration options#12023Conversation
Contributor
size-limit report 📦
|
3 tasks
lforst
approved these changes
May 14, 2024
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
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 forward-ports the
interactionsSampleRateoption forbrowserTracingIntegrationintroduced in 7.110.0 to v8. Looks like we missed this when forward-porting the INP implementation as reported in #12006, probably because these two things happened in parallel.Generally, this PR orients itself on #11382 but I made a couple of changes (that are not API-breaking):
startInactiveSpanwithstandalone: true. This function internally samples the span based ontracesSampleRateand the usual sampling controlling SDK options. In an effort to keep things simple, I opted to simply sample twice - once oninteractionsSampleRateand afterwards ontracesSampleRate. Unless my basic math skills left me, this should lead to the same outcome as sampling once oninteractionsSampleRate * tracesSampleRate.1. In v7, we discarded all INP spans in case of an invalid rate but given we switched defaults for recording and sending INP spans I think we're fine with defaulting to 100%.Gonna tag @edwardgou-sentry please also take a look 🙏
closes #12006