Core concepts
| Name | Description |
|---|---|
| RUM (Real User Monitoring) | RUM (Real User Monitor) helps developers understand actual user experience and optimize application performance by collecting and analyzing performance data from real users using websites or applications |
| Session | Sessions are the core unit of RUM data aggregation, used to analyze user journeys and experiences |
| View | Views record page load times, resource requests, and so on, core to performance monitoring |
| Action | Used to analyze user behavior, measuring interaction performance and frustration points (such as “rage clicks”) in user experience |
| Resource | Analyze resource loading times and performance to optimize page load speed |
| Error | Used to monitor frontend stability and identify errors affecting user experience |
| Long Task | RUM captures long tasks to identify performance bottlenecks causing page stuttering or poor user experience |
| Issue | Issues are the core of error management, used to aggregate similar errors, prioritize problems, and combine context to help developers quickly locate and fix issues |
Performance metrics
| Name | Description |
|---|---|
| Core Web Vitals | RUM monitors these metrics to evaluate webpage loading and interaction performance |
| LCP (Largest Contentful Paint) | Measures page loading performance, recording the time when the main content of the page finishes loading |
| INP (Interaction to Next Paint) | Measures overall interaction responsiveness, recording the latency of all user interactions with the page |
| FCP (First Contentful Paint) | Records when the browser first renders text, images, or other content |
| FID (First Input Delay) | A supplementary metric that records the delay from a user’s first interaction with the page to the browser’s response |
| CLS (Cumulative Layout Shift) | Measures page visual stability, recording unexpected layout shifts that occur during page loading |
| TTFB (Time to First Byte) | Measures server response speed, recording the time from when the request is sent to when the first byte is received |
Data analysis
| Name | Description |
|---|---|
| Attribute | A key-value field attached to an event, such as view_url or resource_status_code. You can filter and group by it in the explorer |
| Global Context | Custom attributes set with the SDK’s setGlobalContext(). They are written to the context field of subsequent events |