What Is Real User Monitoring (RUM)?

real user monitoring (rum) is a performance monitoring practice that is used to observe and measure the performance of a website or an application from the users' perspective rum captures data on how real users interact with the system in real time, which includes metrics like page load times, transaction speeds, error rates, and user behavior patterns this data provides insights into how users directly experience the system using this data, developers can identify and address performance bottlenecks, understand user behavior, and improve overall user satisfaction of their websites or applications real user monitoring with kloudmate rum must be integrated with an apm backend such as kloudmate for the rum data to be utilized effectively this integration is essential as the apm backend, kloudmate in this case, provides the necessary infrastructure and tools to aggregate, process, and analyze the rum data how does rum work? rum works by embedding small javascript snippets into web pages while they are in use these snippets record and send performance metrics back to a monitoring platform where the data can be queried and visualized the collected data is then analyzed using the monitoring platform's monitoring capabilities to understand various performance aspects the following diagram illustrates the step by step process of how real user monitoring (rum) works 1\ user interaction a website user interacts with the rum instrumented website or application, initiating various actions like accessing the website, navigating pages, clicking buttons, or submitting forms 2\ rum instrumentation the front end of the web page that is being accessed is instrumented with rum scripts, which include embedded javascript snippets as the user continues interacting with the page, the rum sdk will collect data on various performance metrics, such as page load times, resource loading times, and user interactions 3 data collection the collected data is sent back to kloudmate kloudmate then aggregates the data and allows for real time monitoring and analysis 4 analysis & visualization kloudmate creates a default dashboard dedicated to visualizing the collected rum data this dashboard is pre populated with all the critical information such as avg lcp, cls, inp, etc , and can be accessed within kloudmate's rum interface key concepts in rum term description trace a trace is a detailed sequential record of operations that occur within an application and its services during the execution of a particular user request or transaction span a span represents a single operation within a trace each span includes metadata such as the start and end time, operation name, and other relevant details session a session is a period during which a user interacts with an application or a website it starts when the user first accesses the web or application page and ends after a predetermined period of inactivity or when the user closes the application user journey the paths that users take through a website, including the sequence of pages and interactions session id a session id is a unique identifier assigned to each user session the session id helps in correlating various user activities and interactions in a session, such as page views, clicks, form submissions, and other events, into a single coherent session session replay a feature within kloudmate that allows capturing and replaying user interactions with a website for analysis network response time the time it takes for a network request made by the user's browser to receive a response from the server web vitals a set of metrics to quantify essential aspects of web page performance, including largest contentful paint (lcp) measures the time it takes for the largest visible content element in the viewport to render from when the page starts loading cumulative layout shift (cls) measures the sum of all unexpected layout shifts that occur during the entire lifespan of the page interaction to next paint (inp) captures the time between the user interaction and the next paint event (which is when the browser updates the page to reflect the result of the said user interaction) first input delay (fid) the delay between the first user interaction with the page (like clicking a link or tapping a button) and the time when the browser begins processing that interaction related resources get started with real user monitoring (rum) https //docs kloudmate com/get started with rum rum interface https //docs kloudmate com/rum interface