Real user monitoring
Page Module:Message box/ambox.css has no content.
| File:Text document with red question mark.svg |
Real user monitoring (RUM) is a passive monitoring technology that records all user interaction with a website or client interacting with a server or cloud-based application.[1] Monitoring actual user interaction with a website or an application is important to operators to determine if users are being served quickly and without errors and, if not, which part of a business process is failing.[2] Software as a service (SaaS) and application service providers (ASP) use RUM to monitor and manage service quality delivered to their clients. Real user monitoring data is used to determine the actual service-level quality delivered to end-users and to detect errors or slowdowns on websites.[3] The data may also be used to determine if changes that are propagated to sites have the intended effect or cause errors.
Organizations typically use RUM to test changes within the production environment or to anticipate behavioral changes in a website or application by using A/B testing or other techniques. As technology shifts more and more to hybrid environments like cloud, fat clients, widgets, and apps, it becomes more and more important to monitor the usage of applications from within the client itself.
Real user monitoring is typically "passive monitoring" i.e., the RUM device collects web traffic without having any effect on the operation of the site. In most cases, a form of JavaScript is injected into the page or native code within the application to provide feedback from the browser or client. This data is collected from various individuals and consolidated.[4]
RUM can be very helpful in identifying and troubleshooting last-mile issues. RUM differs from synthetic monitoring in that it relies on actual people clicking on the page to take measurements rather than automated tests simply going over a given set of test steps.
RUM feature is available in various observability products such as Dynatrace,[5] New Relic.[6] For example, New Relic provides RUM as a part of its Browser monitoring feature in which it captures, processes and visualizes the data in RUM dashboards.[7]
References
Page Template:Reflist/styles.css has no content.
- ^ Page Module:Citation/CS1/styles.css has no content.Altvater, Alexandra (2020-01-29). "What Is Real User Monitoring? How It Works, Examples, Best Practices, and More". Stackify. Retrieved 2022-08-13.
- ^ Page Module:Citation/CS1/styles.css has no content."Real user monitoring (RUM)". Dynatrace. Retrieved September 20, 2021.
- ^ Page Module:Citation/CS1/styles.css has no content."USER EXPERIENCE MONITORING". UTP. 12 June 2014. Retrieved 5 November 2014.
- ^ Page Module:Citation/CS1/styles.css has no content.Oyama, Katsunori; Takeuchi, Atsushi; Ming, Hua; Chang, Carl K. (December 2011). "A Concept Lattice for Recognition of User Problems in Real User Monitoring". 2011 18th Asia-Pacific Software Engineering Conference. Ho Chi Minh, Vietnam: IEEE. pp. 163–170. doi:10.1109/APSEC.2011.32. ISBN 978-1-4577-2199-1. S2CID 7779708.
- ^ Page Module:Citation/CS1/styles.css has no content.Hawes, Carry (13 January 2022). "What is real user monitoring (RUM)?". Dynatrace news. Retrieved 26 April 2025.
- ^ Page Module:Citation/CS1/styles.css has no content."Browser Monitoring | New Relic". newrelic.com. Retrieved 26 April 2025.
- ^ Page Module:Citation/CS1/styles.css has no content."What is Real User Monitoring (RUM)? | New Relic". newrelic.com. 10 December 2024. Retrieved 26 April 2025.
