You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/real_user_monitoring/rum_without_limits/_index.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ RUM without Limits provides you flexibility over your RUM sessions volumes by de
26
26
27
27
Even if you retain only a fraction of your sessions, Datadog provides [performance metrics][1] for all ingested sessions. This ensures an accurate, long-term overview of application health and performance, even if only a fraction of session data is retained.
28
28
29
+
**Note**: In RUM without Limits mode, you can only use default filters on the [Performance Monitoring Summary page][7]. This lets you see the entire dataset and prevents skewed performance metrics since the data is sampled and there are fewer tags available than in event attributes.
30
+
29
31
This page identifies key components of RUM without Limits that can help you manage your RUM sessions volumes within your observability budget.
30
32
31
33
### For new applications
@@ -81,7 +83,7 @@ To alleviate this, set `traceSampleRate` to a percentage below 100% (to the prev
81
83
82
84
On mobile applications, many concurrent versions can live together. However, existing versions are not necessarily sending 100% of sessions, which means that creating new retention filters reduces the data available in Datadog for these application versions.
83
85
84
-
Datadog recommends creating the same retention filters for all application versions, independently of whether the SDK sampling rate is set to 100% or not. Ultimately, all valuable sessions will still end up being collected even if some sessions are not ingested for some older versions.
86
+
Datadog recommends creating the same retention filters for all application versions, independently of whether the SDK sampling rate is set to 100% or not. Ultimately, all valuable sessions are still collected even if some sessions are not ingested for some older versions.
85
87
86
88
See suggested retention filters and use cases in [Retention Filter Best Practices][5].
87
89
@@ -99,3 +101,4 @@ Create and configure [retention filters][6].
0 commit comments