Product Introduction
Overview
RUM records sessions, page performance, errors, and release changes from real browser visits. After a web application loads the snippet, you can inspect sessions, Core Web Vitals, errors, releases, and conversion paths, and alert when an experience metric crosses a threshold.
APM looks at calls between services. RUM looks at what happens after a person opens a page: load, interaction, errors, and whether the key path was completed. The two modules can run together, but they onboard different targets and use different metrics.
Core Advantages
-
Copy a snippet per application
After you create an application, copy the npm, React, CDN, or generic snippet. The setup list marks an application as Connected, Not connected, or Disabled from whether data was recently accepted and stored. -
Sessions, performance, and errors share one time range
Experience covers sessions, page performance, and funnels. Quality covers errors and releases. Lists filter by application and time range. A session can open its detail and replay. -
Compare experience by release
Releases summarize versions. After you select one application, you can mark an experience baseline and compare later versions. Upload a source map to restore minified stacks. A CI token is shown in full only once, when it is created or rotated. -
Experience alerts and erasure are separate
Policies cover error rate, LCP, INP, CLS, FCP, TTFB, and session count. Governance can erase collected data for an application and user id, and keeps the erase job.
Use Cases
-
Check whether a release made pages slower
Compare LCP and INP in Views and Releases after the snippet is receiving data. -
Replay the visit that hit an error
Sort sessions by Impact, Errors, or Duration, open the replay, then open the grouped error. -
See whether a key path finishes
Define funnel steps as page routes and read arrivals and conversion. -
Erase one user's experience data
Submit an erase job with the application and user id, then check the job list.