Feature Overview

RUM is organized as Experience, Quality, Events, Integration, and Governance.

1. Experience

1.1 Sessions

Sessions are the entry for one real visit.

• Filter by application and time range, and search by session id.
• Sort by Impact, Start time, Errors, or Duration.
• See browser, desktop, tablet, or phone, and the route.
• Open session detail, then replay.
• Export respects the current filters and permissions.
• Traffic can be Visitors, Automated, or All traffic.

1.2 Views and performance

See LCP, INP, FCP, TTFB, and CLS for a page. Timings are milliseconds. Empty means no sample. Distribution and device mix show where the metric landed. Period comparison appears when a comparison window exists. Switch between one application and the summary.

1.3 Funnels

Define 2 to 8 routes, separated by commas, such as /,/checkout,/success. A funnel can be bound to one application. Arrivals and conversion use the current filters. Open a funnel for the step detail.

2. Quality

2.1 Errors

Group similar frontend errors and open the evidence stack. From an error, return to the session and replay when needed.

2.2 Releases

List versions seen in the selected range. The all-application view is a summary. Mark an experience baseline only after selecting one application, then compare later versions. Source map upload requires application, release, deployed artifact path, and file. Rotate the CI token for pipeline uploads. The full token is shown once.

3. Events

3.1 Alerts

List experience alerts by application and time, then return to the policy to change a threshold or disable it.

3.2 Policies

Metrics are error rate, LCP P75, INP P75, CLS P75, FCP P75, TTFB P75, and session count. Comparators are Greater than, Greater or equal, Less than, and Less or equal. Warning and critical thresholds are separate. Severity is Info, Warning, or Critical. Enable or disable a policy without deleting it.

Suggested defaults, which you should still adjust:

Metric	Warning	Critical
Error rate	3%	5%
LCP P75	2500 ms	4000 ms
INP P75	200 ms	500 ms
CLS P75	0.1	0.25
FCP P75	1800 ms	3000 ms
TTFB P75	800 ms	1800 ms

Session count has no suggested threshold.

4. Integration

4.1 Applications

The catalog sorts by health, sessions, and error rate, and shows whether LCP and INP are past the common thresholds. Maintain allowed origins. Open one application for its experience summary. If collection is degraded, the page says why instead of treating empty data as a healthy experience.

4.2 Setup

Copy npm, React, CDN, or generic snippets. Connected means both the latest accept time and store time are within 15 minutes. Not connected means there is no fresh data yet. Disabled means the application is turned off. Filter the list by Not connected or Connected. Use the on-page self-check for snippet, origin, and upload.

5. Governance

5.1 Compliance erase

Submit an erase job with an application and user id. The job list can be filtered by application and searched by user id. The action requires permission.

Note: Erase cannot be undone. Confirm the application and user id before submitting.