---
title: rum.events dataset
description: The predefined rum.events dataset that stores Real User Monitoring events, with its record schema.
url: https://coralogix.com/docs/user-guides/data-layer/default-dataspace/rum-events/
product: dataengine
feature: Dataset Management
feature_id: dataspace-dataset-mgmt
feature_identifier: dataengine/dataspace-dataset-mgmt
last_updated: '2026-10-14'
---

# `rum.events`

## Purpose

The `rum.events` dataset holds the [Real User Monitoring](https://coralogix.com/docs/user-guides/rum/getting-started/real-user-monitoring.md) events your browser SDK sends, such as page loads, user interactions, network requests, web vitals, and errors. It's a [predefined dataset](https://coralogix.com/docs/user-guides/data-layer/default-dataspace/predefined-datasets.md): Coralogix provisions it in the `default` dataspace, and your SDK fills it.

## Query the dataset

```
source default/rum.events

| filter event_context.type == 'network-request'
```

In Explore, select `rum.events` in the dataset selector. Explore gives it its own default grid columns, described in [Select a dataset](https://coralogix.com/docs/user-guides/data_exploration/datasets.md#rumevents).

## Schema description

Every event carries the standard log record envelope: engine metadata in `$m`, labels in `$l`, and the RUM payload in `$d`.

| Field                 | Type               | Required | Description                                                                                              |
| --------------------- | ------------------ | -------- | -------------------------------------------------------------------------------------------------------- |
| `$d`                  | object             | Yes      | Entity-type-specific payload — shape defined by each entity type's schema                                |
| `$l`                  | map                | Yes      | User labels: free-form string-to-string map                                                              |
| `$l.<key>`            | string             | No       |                                                                                                          |
| `$m`                  | object             | Yes      | Engine metadata                                                                                          |
| `$m.cxEventId`        | string (uuid)      | Yes      | Globally unique event id                                                                                 |
| `$m.ingressTimestamp` | string (date-time) | Yes      | Time the event was ingested                                                                              |
| `$m.priorityClass`    | string             | Yes      | Defines the feature-set enabled for the event<!-- --> <!-- -->One of: `high`, `medium`, `low`.           |
| `$m.severity`         | string             | Yes      | Event severity level<!-- --> <!-- -->One of: `Verbose`, `Debug`, `Info`, `Warning`, `Error`, `Critical`. |
| `$m.timestamp`        | string (date-time) | Yes      | Event timestamp                                                                                          |

For every RUM payload field, organized by event type (user interactions, network requests, errors, web vitals, and more), see [Querying RUM logs](https://coralogix.com/docs/user-guides/rum/query-rum-logs.md).

## Next steps

* Route RUM events with TCO policies in [TCO Optimizer](https://coralogix.com/docs/user-guides/account-management/tco-optimizer/create-and-manage-policies.md#rum-policies).
* See the other datasets Coralogix provisions in [Predefined datasets](https://coralogix.com/docs/user-guides/data-layer/default-dataspace/predefined-datasets.md).