Updating RUM sampling rate from UI #33711
Open
+11
−4
Conversation
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
github-actions
bot
added
Images
Contributor
Preview links (active after the
|
rtrieu
commented
Jan 7, 2026
content/en/real_user_monitoring/guide/best-practices-for-rum-sampling.md
Outdated
Show resolved
Hide resolved
maycmlee
approved these changes
Jan 7, 2026
…m:DataDog/documentation into rtrieu/clarify-sampling-retention-filters
MaelNamNam
requested changes
Jan 8, 2026
Contributor
MaelNamNam
left a comment
MaelNamNam
left a comment
There was a problem hiding this comment.
I found the changes to still be a bit confusing so I suggested some improvements to make it clearer. Let me know if those work for you
content/en/real_user_monitoring/guide/best-practices-for-rum-sampling.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/guide/best-practices-for-rum-sampling.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/guide/best-practices-for-rum-sampling.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/guide/best-practices-for-rum-sampling.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Maël Lilensten <[email protected]>
…m:DataDog/documentation into rtrieu/clarify-sampling-retention-filters
rtrieu
commented
Jan 8, 2026
content/en/real_user_monitoring/guide/best-practices-for-rum-sampling.md
Outdated
Show resolved
Hide resolved
…ampling.md Co-authored-by: Rosa Trieu <[email protected]>
MaelNamNam
requested changes
Jan 8, 2026
Contributor
MaelNamNam
left a comment
MaelNamNam
left a comment
There was a problem hiding this comment.
1 link to change and we should be good, thanks!
| During live outages, incidents, or bug investigations, and for customers that are not yet on [RUM without Limits][2] you can increase client-side (head-based) sampling to collect 100% of your sessions to ensure nothing is missed, or to have more examples of a particular issue. | ||
|
|
||
| During live outages, incidents, or bug investigations, you can increase sampling to collect 100% of your sessions to ensure nothing is missed, or to have more examples of a particular issue. | ||
| You can only change the **head-based** sampling rate from the Datadog UI if you use the [**server-side injection method**][17] to add the Browser RUM SDK to your web application. To do this, [modify the sampling rate][15] on the SDK Configuration page. |
Contributor
There was a problem hiding this comment.
Here we're talking about updating head-based sample rate from the RUM x remote config UI, not retention filters
Suggested change
| You can only change the **head-based** sampling rate from the Datadog UI if you use the [**server-side injection method**][17] to add the Browser RUM SDK to your web application. To do this, [modify the sampling rate][15] on the SDK Configuration page. | |
| You can only change the **head-based** sampling rate from the Datadog UI if you use the [**server-side injection method**][17] to add the Browser RUM SDK to your web application. To do this, [modify the sampling rate][17] on the SDK Configuration page. |
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.
What does this PR do? What is the motivation?
Makes it more clear how to update the sampling rate for RUM applications.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes