8000 draft of summary note (#29308) · DataDog/documentation@50065b5 · GitHub
[go: up one dir, main page]

Skip to content

Commit 50065b5

Browse files
authored
draft of summary note (#29308)
1 parent a412d59 commit 50065b5

File tree

1 file changed

+4
-1
lines changed
  • content/en/real_user_monitoring/rum_without_limits

1 file changed

+4
-1
lines changed

content/en/real_user_monitoring/rum_without_limits/_index.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ RUM without Limits provides you flexibility over your RUM sessions volumes by de
2626

2727
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.
2828

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+
2931
This page identifies key components of RUM without Limits that can help you manage your RUM sessions volumes within your observability budget.
3032

3133
### For new applications
@@ -81,7 +83,7 @@ To alleviate this, set `traceSampleRate` to a percentage below 100% (to the prev
8183

8284
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.
8385

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.
8587

8688
See suggested retention filters and use cases in [Retention Filter Best Practices][5].
8789

@@ -99,3 +101,4 @@ Create and configure [retention filters][6].
99101
[4]: https://app.datadoghq.com/rum/list
100102
[5]: /real_user_monitoring/guide/retention_filter_best_practices/
101103
[6]: /real_user_monitoring/rum_without_limits/retention_filters
104+
[7]: https://app.datadoghq.com/rum/performance-monitoring

0 commit comments

Comments
 (0)
0