Overview
Real User Monitoring enables organizations to gain visibility into how users experience their frontend applications. Kloudfuse RUM enables answer questions such as:
What parts of my application are users spending the most time on?
Which parts of the world are my users coming from?
What pages have the lowest web vital scores such as LCP, FCP, INP?
What resources are contributing to my applications slowness?
What kinds of errors and frustrations are users experiencing?
Kloudfuse RUM additionally offers a powerful user session recording and replay feature providing a high fidelity video like visualization of a users journey through your application.
Kloudfuse RUM Events
The Kloudfuse RUM SDK instruments your frontend application and emits events with a rich set of attributes that allows you to access unique insights. A typical user session on a frontend application will involve multiple page navigations, multiple user interactions such as clicks and taps, resource loads and api calls to fetch data from backends. Kloudfuse RUM emits the following types of event:
View: A view event corresponds to a logical page navigation. All user activity and background activity occurs under the context of a page.
Action: An action event corresponds to a user interaction such as a click or a tap.
Resource: A resource event corresponds to a network call to fetch some data. This include static assets such as javascript and css as well as XHR and fetch API calls that retrieve data from backend applications.
Error: An error event carries information about unhandled errors produced either by your application or by the libraries your application uses and typically carries a stacktrace.
Long Task: A long task event corresponds to instances where the browser is unable to be responsive to user interaction (a situation typically caused by heavy data processing on the client side or bugs).
Session: A session is a derived concept that ties together all of the other kinds of events that occur during a users journey through a web application.
Resource, Error and Long Task events may also be automatically associated with a specific Action event. As an example a user interaction such as a click may lead to request to fetch required data over the network to render a widget on the current page.