Real user monitoring

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 web sites.[3] The data may also be used to determine if changes that are propagated to sites have the intended effect or cause errors.

Organisations typically use RUM to test changes within the production environment, or to anticipate behavioural 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.

RUM can be very helpful in identifying and troubleshooting last mile issues. Real User Monitoring 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 software

References
  1. "WHAT IS REAL-USER MONITORING?". alertsite.com. January 28, 2014. Retrieved June 27, 2014.
  2. "REAL USER MONITORING (RUM)". Dynatrace. Retrieved 5 November 2014. All this data gives you new ability to analyze which application transactions your users are performing and what application response they are experiencing.
  3. "USER EXPERIENCE MONITORING". UTP. Retrieved 5 November 2014.
  4. https://matomo.org/faq/new-to-piwik/how-do-i-get-rum-real-user-monitoring-metrics-and-reports-for-my-app-website-and-intranet/
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.