Real User Monitoring (RUM)

RUM is an acronym for Real User Monitoring, a technology that measures and tracks the end-user experience of an application or website. It is a core feature of APM, and a key component for gaining real-world observability into web performance and service availability.

Kloudfuse Digital Experience Monitoring (DEM)

Watch our feature overview for RUM, a significant component of DEM.

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 the slowness in my application?

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

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 navigation, multiple user interactions (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 includes 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 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. For example, a user interaction such as a button click may lead to network requests to fetch required data needed to render a widget on the current page. The resource events corresponding to these network requests will automatically be associated with the specific action event trigger.

Next steps