[DOCS-12674] Update RUM alerting guide #33053
Open
+60
−39
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
|
Contributor
|
Created a docs card: https://datadoghq.atlassian.net/browse/DOCS-12782 |
MaelNamNam
requested changes
Nov 25, 2025
| - **Build a custom monitor**: Choose from out-of-the-box metrics or custom metrics, then scope to your application, specific pages, or views. | ||
|
|
||
| The example above is a search query for a RUM monitor configured for views on the Shopist iOS application with facets such as `Application ID` and `View Path`. This example monitor alerts when a view has a high amount of errors (for example, more than 8). | ||
| Learn more about [creating RUM Monitors][4]. |
Contributor
There was a problem hiding this comment.
Should we also update /monitors/types/real_user_monitoring? It's outdated too
Comment on lines
68
to
74
| ### Error rates | ||
|
|
||
| The ratio of errors to requests allows you to calculate what percentage of requests are resulting in errors. | ||
| The ratio of errors to requests shows what percentage of requests result in errors. | ||
|
|
||
| This example shows a RUM monitor for the error rate of the `/cart` page on a sample Shop.ist application. | ||
|
|
||
| {{< img src="real_user_monitoring/guide/alerting-with-rum/error-rate-example-monitor.png" alt="RUM monitor for error rates" style="width:100%;" >}} |
Contributor
There was a problem hiding this comment.
This is an event-based example, while we have out-of-the-box metrics for RUM without Limits customers for this. I would delete this section all together
Comment on lines
+78
to
+80
| Real User Monitoring measures, calculates, and scores application performance as [Core Web Vitals][10] and [Mobile Vitals][11]. For example, Largest Contentful Paint (LCP) measures loading performance. A widely used benchmark is 2.5 seconds when the page starts loading. | ||
|
|
||
| This example shows a RUM monitor for the LCP of the `/cart` page on a sample Shop.ist application. | ||
| This example shows a RUM monitor for the LCP metric filtered to a specific application (for example, `Shop.ist`) and grouped by `view name` to track performance across different pages. Grouping by view name helps pinpoint which pages have performance issues. |
Contributor
There was a problem hiding this comment.
The screenshot shows the INP metric, not the LCP. I don't mind advertising one or the other, but I just believe we should remain consistent
Co-authored-by: Maël Lilensten <mael.lilensten@datadoghq.com>
MaelNamNam
requested changes
Nov 26, 2025
| {{< img src="real_user_monitoring/guide/alerting-with-rum/export-to-monitor-3.mp4" alt="Export button to the right hand corner of the RUM Explorer" video="true" style="width:100%;" >}} | ||
| - **Visibility into your full traffic**: Metrics are computed over your full, unsampled traffic before retention filters apply to provide broader visibility into application health | ||
| - **Reduce the risk of missing issues**: Event-based monitors depend on retention filters and can miss issues if relevant events aren't indexed | ||
| - **Advanced capabilities**: Metric-based monitors support anomaly detection, outlier detection, and forecasts |
Contributor
There was a problem hiding this comment.
Sorry I missed this one
Suggested change
| - **Advanced capabilities**: Metric-based monitors support anomaly detection, outlier detection, and forecasts | |
| - **Advanced capabilities**: Metric-based monitors support anomaly detection |
Contributor
There was a problem hiding this comment.
@rtrieu as I mentioned the text calls the LCP out while the screenshot shows the INP metric. Could you update the screenshot to show an LCP-based monitor and remain consistent with the rest of the paragraph please?
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?
Updates images and text for the RUM alerting guide to focus more metrics-based instead of events-based alerting.
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