rum.events
Purpose
The rum.events dataset holds the Real User Monitoring events your browser SDK sends, such as page loads, user interactions, network requests, web vitals, and errors. It's a predefined dataset: 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.
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.
Next steps
- Route RUM events with TCO policies in TCO Optimizer.
- See the other datasets Coralogix provisions in Predefined datasets.
Last updated on