![]() |
VOOZH | about |
Datadog’s RUM without Limits provides an accurate, long-term overview of application health and performance, even if only a fraction of session data is retained by retention filters. But any session can be useful to solve an unexpected support ticket, perform a compliance audit, or conduct a retroactive investigation.
RUM Managed Archive acts as a safety net, enabling teams to:
Common use cases include:
After you enable Managed Archive, all ingested sessions (excluding Synthetic Monitoring sessions) are stored automatically for the configured storage period. These sessions are accessible in a dedicated Managed Archive UI, separate from the RUM Explorer.
All stored sessions, including sessions retained by retention filters or already recovered, are shown in the Managed Archive UI. A set of session tags and attributes are available to help you navigate and identify sessions to recover:
| Attribute | Description |
|---|---|
@account.id | Account ID |
@application.id | RUM application ID |
@session.id | Unique session ID |
@timestamp | Timestamp of the session |
@usr.anonymous_id | Anonymous user ID |
@usr.id | User ID |
country | Country of the session |
service | Service name |
version | Application version |
Once a session is recovered, the corresponding row in the Managed Archive UI is visually marked and the session becomes available in the RUM Explorer.
Access to Managed Archive and Recovery is controlled through role-based access control (RBAC):
| Permission | Capability | Default Role |
|---|---|---|
| RUM Managed Archive Read | View the Managed Archive configuration and stored sessions, but cannot edit the configuration or recover sessions | Standard |
| RUM Managed Archive Config Write | Turn session storage on or off for an application | Admin |
| RUM Recovery Index | Recover sessions | Admin |
To enable session storage for an application:
Configuration is done at the application level, which means you can apply different storage strategies per application.
In the Managed Archive UI, click Recover on the row of the session you want to recover.
Recovered sessions are available for 30 days with all their events and attributes. Recovered sessions have the same investigation capabilities as sessions retained by a retention filter
After recovering a session, find it in the RUM Explorer by querying on:
@session.retention_reason:recovery@session.matching_retention_filter.name:recovery@session.matching_retention_filter.id:recoveryRecovered sessions that were initially retained by a retention filter have @session.was_retained:true.
Additional helpful documentation, links, and articles:
| |