RUM Event Attributes
Every RUM event type carries its own set of attributes on top of the shared session, device, browser, and geo context described in RUM Explorer. This page describes the four child event types that make up a user session — Views, Actions, Resources, and Errors — with an attribute reference for Actions and Resources; browse them live from RUM > Explorer by setting Event Type — see Event Types.
Views
View events represent navigation to different parts of your frontend application. This includes page loads and transitions within a single page application.
A view event holds attributes such as the Page URL and also includes rich statistics including Web Vitals such as First Contentful Paint (FCP), Largest Contentful Paint (LCP), Interaction to Next Paint (INP) as well as timing statistics such as DOM Interactive and DOM Content Loaded.
All user interactions (Action events), resource loads (Resource events), and other RUM event such as Error and Long Task events occur in the context of an active view and view events maintain aggregate statistics across these child events.
Opening a view event shows its full attributes, Web Vitals, and child Action/Resource/Error/Long Task counts in the event detail panel, and its Performance tab breaks down the same timing data shown in aggregate on RUM Performance.
Actions
An action corresponds to a user activity such as a click, a tap, a scroll etc. From the observability perspective, an action has quite a few important properties that can provide insights into users' behavior patterns. They also inherit properties from the active parent view.
- Action.id
-
Unique identifier for every action.
- Action.name
-
Concatenation of the user activity and the UI element (target) it was performed on. Many distinct actions may have the same name eg a user clicking the same button twice or two different users clicking on the same button in separate sessions.
- Action.loading_time
-
The loading time of the action. It is calculated from the time the user interacts with a UI target to the time that the page has no more activity.
- Action.long_task.count
-
Any browser task that blocks the main thread for more than 50ms is a
long_task. - Action.resource.count
-
A resource event is triggered for a resource fetch such as images, XHR, Fetch, CSS, or JS libraries loaded on a webpage.
- Action.error_count
-
The number of errors that occurred during the action.
Resources
A resource event corresponds to a resource or asset fetch on a webpage such as an image, XHR, Fetch, CSS, or JS library. A resource is a child event to an action event. It also has the context of the view that is currently active. If RUM and APM are linked, a resource whose backend request was traced carries a link to that trace.
The following properties may be used to analyze and profile resources in a session:
- duration
-
Overall time spent fetching the resource
- resource.size
-
Resource size
- resource.connect.duration
-
Time to establish connection to resource server
- resource.ssl.duration
-
TLS handshake time for HTTPS connections
- resource.dns.duration
-
DNS resolution time
- resource.redirect.duration
-
Time spent following HTTP redirects before the final request
- resource.first_byte.duration
-
Waiting time to receive the first byte of the resource
- resource.download.duration
-
Response download time
- resource.type
-
Type of resource being fetched.
- resource.method
-
HTTP method
- resource.status_code
-
Response code
- resource.url
-
URL of the resource being fetched
- resource.url_host
-
URL host
- resource.url_path
-
URL path
- resource.url_query
-
URL query parameters
- resource.url_scheme
-
Protocol type
- resource.provider.name
-
Resource provider name
- resource.provider.domain
-
Resource domain
- resource.provider.type
-
The type of content provider
Errors
RUM Errors captures frontend errors that occur in your application, including both unhandled exceptions and errors explicitly reported by your code. Each error event records the error message and stack trace when available, and Kloudfuse automatically groups similar errors together for easier analysis and troubleshooting.
The Errors event type in the Explorer has an Error Groups sub-tab that clusters similar errors by their message and stack trace, showing the error Type, originating Service, Occurrences, and First seen/Last seen timestamps for each group — the same summary that the Performance screen’s Errors tab surfaces as Ongoing issues.
Open any error event or error group to see its full message and stack trace in the event detail panel. If RUM and APM are linked, errors that occurred during a traced backend call also carry a link to that trace.