RUM

Quickly see how real users experience your app and catch front-end issues early.

The RUM page in groundcover lets you monitor real user activity on your web application. It highlights key performance metrics (like web-vitals and page load times), error rates, and user behavior.

This helps you understand what real users are facing – for example, identifying slow page load times, spotting frequent errors, or seeing which pages are most popular – so you know where to focus your attention.

The Real User Monitoring summary page has three main sections:

1. A summary cards,

2. Trend charts (Exceptions over Time, Sessions over Time) and a list of visited pages,

3. A table with detailed sessions table

Summary Cards

At the top of the RUM page, you’ll see five summary cards showing key user experience stats. These cards give a quick health check of your front-end performance:

• Avg INP (input delay): The average delay after a user interaction (like clicking a button) before the page responds. A lower number means the app feels snappy; a high number indicates users might be waiting too long for feedback.

• Avg CLS (layout shift): The average Cumulative Layout Shift score, measuring how much the page content jumps around during load.

• Page Load Time: The average time it takes for pages to fully load for users, measured in milliseconds. This reflects your site’s loading speed.

• Error Rate: The percentage of user sessions that encountered an error (for example, JavaScript exceptions).

• User Count: The number of unique user sessions in the selected time frame. This shows how many distinct users (or sessions) have been recorded.

Sessions Table

At the bottom of the RUM page, you’ll find a detailed sessions table listing individual user sessions. Each row in this table represents one user’s session on your app, with key details to help you trace their experience. Important columns include:

• Date/Time: When the session occurred (start time or timestamp of the session).

• User (Email/ID): The user’s identifier, which could be an email, username, or “Anonymous” if the user isn’t logged in. This helps identify the session’s user if needed.

• Errors: How many errors occurred during that session (e.g. count of exceptions). If this number is greater than 0, it means the user encountered problems.

• Pages: The number of pages the user visited in that session. A higher page count might indicate a longer session or a user navigating through many parts of the app.

• Duration: How long the session lasted (for example, “07:36” means 7 minutes 36 seconds). This shows if the user spent a long time (possibly struggling) or left quickly.

• Browser: The browser used in the session (often shown by an icon or name like Chrome, Safari, etc.). This can reveal if an issue is browser-specific (e.g. all errors happening on one browser).

• Device: The type of device (e.g. desktop, mobile) indicated by an icon. This helps you see if mobile users vs. desktop users have different experiences.