fix: Fix issue with errors forcefully triggering session traces #819
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.
Fixing an issue where an uncaught error or calls to the
noticeError
API would force session trace to begin collecting and harvesting data, even though session trace and session replay were disabled via the RUM response.Overview
With the recent session replay API merge, an error thrown on a page or passed in using the
noticeError
API method would cause session trace to switch to full mode. This was due to session trace not accounting for the current session replay mode when switching modes. If session replay is disabled, session trace should not switch modes at all from it's initial mode.Related Issue(s)
https://newrelic.pagerduty.com/incidents/Q05RP88T92MSAS/
#803
Testing
Full suite passed locally. Seeking merge due to time constraints for active incident