-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Reduce sample rate for RUM sessions #17443
Conversation
Warning There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure. 🔧 eslint
warning [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options. WalkthroughThe pull request modifies the Changes
Suggested labels
Suggested reviewers
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
libs/user-monitoring/src/lib/user-monitoring.ts (1)
21-21
: Document the sampling rate change.Consider adding a comment explaining why 10% was chosen as the optimal sampling rate to help future maintainers understand the decision.
+ // Sampling 10% of sessions provides sufficient monitoring coverage while optimizing costs sampleRate: 10,
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
libs/user-monitoring/src/lib/user-monitoring.ts
(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
libs/user-monitoring/src/lib/user-monitoring.ts (1)
Pattern libs/**/*
: "Confirm that the code adheres to the following:
- Reusability of components and hooks across different NextJS apps.
- TypeScript usage for defining props and exporting types.
- Effective tree-shaking and bundling practices."
🔇 Additional comments (2)
libs/user-monitoring/src/lib/user-monitoring.ts (2)
21-21
: LGTM! Consider monitoring coverage impact.The reduction in sample rate to 10% aligns with the PR objective. This change will significantly reduce data collection volume while maintaining monitoring capabilities.
Please monitor these metrics after deployment to ensure adequate coverage:
- Error detection rates
- Performance metrics reliability
- User journey tracking completeness
21-21
: Verify monitoring coverage requirements.Let's ensure this sampling rate meets your monitoring SLAs and requirements.
Run this script to check current RUM usage patterns:
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17443 +/- ##
==========================================
- Coverage 35.67% 35.66% -0.01%
==========================================
Files 6938 6938
Lines 149103 149103
Branches 42636 42636
==========================================
- Hits 53187 53184 -3
- Misses 95916 95919 +3 Flags with carried forward coverage won't be shown. Click here to find out more. see 3 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportAll test runs ✅ 10 Total Test Services: 0 Failed, 10 Passed Test ServicesThis report shows up to 10 services
🔻 Code Coverage Decreases vs Default Branch (5) |
Summary by CodeRabbit