Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion content/en/real_user_monitoring/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,27 @@ Datadog's *Real User Monitoring (RUM)* gives you end-to-end visibility into the
* **Analytics / Usage**: Understand who is using your application (country, device, OS), monitor individual users journeys, and analyze how users interact with your application (most common page visited, clicks, interactions, and feature usage).
* **Support**: Retrieve all of the information related to one user session to troubleshoot an issue (session duration, pages visited, interactions, resources loaded, and errors).

A user session is a user journey on your web or mobile application lasting up to four hours. A session usually includes pageviews and associated telemetry. If a user does not interact with an application for 15 minutes, the session is considered complete. A new session starts when the user interacts with the application again.
### Session definition

A user session is a user journey on your web or mobile application. A session includes all of its constitutive navigation events (RUM Views), user actions (RUM Actions), network requests (RUM Resources), crashes and errors (RUM Errors), and many more events and signals that all together produce a faithfull picture of the user experience.

A RUM session can last up to 4 hours, and expires after 15 minutes of inactivity. If the user interacts with the application again after those limits, a new session is automatically create.

### Technical limitations

| Property | Limitation |
| ------------------------------------------ | ------------------------ |
| Maximum duration of a session | 4 hours |
| Timeout of a session | 15 minutes of inactivity |
| Maximum number of events per session | 30 million |
| Maximum number of attributes per event | 1,000 |
| Maximum attribute depth per event | 20 |
| Maximum event size | 1 MB |
| Maximum intake payload size | 5 MB |
| Maximum source maps and mapping files size | 500 MB per file |
| Maximum dSYM files size | 2 GB per file |
| Maximum delay at ingestion | 24 hours – beyond this limit, events uploaded by the SDK are dropped by our intake |


## What is Session Replay?

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -112,14 +112,7 @@ The example code creates the following action event:
}
```

If an event or a request goes beyond any of the following limitations, it is rejected by the Datadog intake.

| Property | Limitation |
| ---------------------------------------- | ------------ |
| Maximum number of attributes per event | 256 |
| Maximum attribute depth per event | 20 |
| Maximum event size | 256 KB |
| Maximum intake payload size | 5 MB |
If an event or a request goes beyond any of limitations listed [here][], it is rejected by the Datadog intake.

## "Customer data exceeds the recommended threshold" warning

Expand Down Expand Up @@ -160,3 +153,4 @@ A warning appears when deobfuscation fails for a stack trace. If the stack trace
[13]: /real_user_monitoring/application_monitoring/browser/setup/#initialization-parameters
[14]: https://app.datadoghq.com/source-code/setup/rum
[15]: /real_user_monitoring/guide/debug-symbols
[16]: /real_user_monitoring/#technical-limitations
Loading