> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/rum.md).

# Real User Monitoring

The **Real User Monitoring** 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 two main sections:

1. Trend charts (Exceptions over Time, Sessions over Time) and a list of visited pages,
2. A detailed sessions table

### 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.

### Session Details

Selecting a session opens the **session drawer**, showing a full, ordered timeline of the user’s experience — clicks, navigations, network requests, logs, custom events, and errors — alongside the session recording when one is available.

Use **Explain this session** to have [Agent Mode](/use-groundcover/agent-mode.md) summarize the journey in natural language and highlight the events that led to an issue, so you can understand what happened without replaying the whole session.

### Exceptions

Front-end exceptions have a dedicated exploration view for triaging client-side errors, with full stack traces, contextual data, and **AI root-cause analysis**. See [Real User Monitoring (RUM)](/capabilities/real-user-monitoring-rum.md#exception-exploration) for the full capability overview.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/rum.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.