In this course, we talk about basic concepts in Real User Monitoring (RUM), and we touch on the mechanics of how RUM works. If you are already familiar with RUM, you may want to move on to Setting up Real User Monitoring. No Worries. We won't tell.

What is Real User Monitoring?

When it comes to measuring the performance experienced by your site's actual users, you can't beat Real User Monitoring (RUM). RUM records your RUM enabled page's performance, aggregates the data, and displays the data in interactive dashboards where you can compare performance based on page viewed, device, browser and version, operating system and version, and user location.

RUM is a passive approach to monitoring because it relies on your users accessing your site to generate data. If your site goes down, your users can't access the site, and, as a result, there is no data to report. That is where your synthetic or active monitoring comes in. Your synthetic monitors such as Uptime Monitors, Performance Monitors, API Monitors, and Transaction Monitors check your site on a regular basis, and if they experience a problem, we let you know about it right away using your alerting settings.

How does Real User Monitoring work?

You place a tiny, non-invasive script in the <head> tags on the pages you would like to track with RUM. When your users access a RUM enabled page, the script records the page's performance. Once the page finishes loading, the script bundles the performance data with information about the user's environment and location and sends it to the cloud. Uptrends retrieves the data in almost real time and displays it in your rum dashboards. The result is a comprehensive picture of your site's actual performance as experienced by your users. If you're concerned about user privacy, we've got you covered.

What does a RUM Script look like?

Our engineers designed the RUM script to be as non-invasive as possible. The small script loads fast with virtually no impact on page performance. It does its work in the background as the page load progresses, and after the page load completes, the script finishes by sending the user data and performance data to the cloud. Your script will look similar to the script below.


                var _urconfig = { sid: "9acad2af-b1f5-4438-8de6-5047a02a7ecf", aip: 0, usePageProtocol: false };

                (function (d, s) {

                   var js = d.createElement(s),

                       sc = d.getElementsByTagName(s)[0];

                   js.src = "";

                   js.async = "async";

                   sc.parentNode.insertBefore(js, sc);

                }(document, "script"));