Browser Real User Monitoring

Browser Real-User Monitoring (Browser RUM) allows you to see how your web application is performing from the point of view of a real or synthetic end user. You can answer questions like:

• Which 1st or 3rd-party Ajax or iframe calls are slowing down page load time?
• How does server performance impact end user experience in aggregate or in individual cases?

You can drill into the data to explore how users experience your application in their web browsers.

Monitor your Application

Browser RUM offers multiple ways to look at your data in real time. You can: 

• Understand and improve your web page's performance
  • Know how your pages, Ajax requests, and iframes are performing over time. See The Pages & Ajax Requests View.
  • Gain insight into individual requests, with detailed charts on how your pages, Ajax requests, and iframes load and build in your end user's browsers, with links, if enabled, to reports on server-side performance. See Browser Snapshots.
  • Find your worst performing pages by multiple common metrics. See Top Pages.
• Reduce errors
  • Learn which pages are loading with JavaScript errors, and the script file and line number that are creating the problem. See Browser Snapshots.
• Learn about your users
  
  • See how your web users are connecting to your application by device/platform and browser. See Browser App Dashboard.
  • Find out where in the world your web users are and how your application is performing across countries and regions. See Browser App Dashboard.
  • Understand how users are navigating through your website and what actions they are taking. See Browser RUM Sessions.

For more information on using Browser RUM, see Monitor Your Applications with Browser RUM.

How It Works

The JavaScript Agent is made of up two small JavaScript files, adrum.js and adrum-ext.js.

1. The file adrum.js is injected into each instrumented page, as close to the top as possible, as the page is served. Although it loads synchronously, it's a very small file, around 30 KB (10 to 12 KB with compression), and generally, executes in less than 5 ms in modern browsers and less than 15 ms in older browsers.
2. This first JavaScript file starts a timer and does some quick configuration and setup.
3. At the onload event, adrum-ext.js is fetched asynchronously, specifically to not block the page from loading. This is the code that does most of the heavy lifting. Once it has been fetched, it is cached for 24 hours on the browser. 
4. When cross-domain session correlation is enabled, the first time a user visits a domain, the browser additionally loads the file adrum-xd.html to generate or load a piece of common information that enables cross-domain sessions. Future visits will not load adrum-xd.html again.
5. When the page has completed loading, the collected data is bundled into a beacon and sent to the EUM Cloud by adrum-ext.js. 
6. The data is processed by the EUM Cloud and then made available for pickup by the Controller.

For more detailed information, check out the video below.

Watch the Video

For full-screen viewing, click Start Monitoring with Browser Real User Monitoring (RUM).

Set Up and Configure Browser RUM

Browser RUM is easy to set up. It is also highly configurable. You can:

• Set up and enable Browser RUM. See Set Up and Access Browser RUM.
• Instrument your application to work with Browser RUM. For more information, see Configure the JavaScript Agent.
• Set up how your information appears in the Controller UI. For more information, see Configure the Controller UI for Browser RUM.

License and Enable Browser Monitoring

Browser Real-User Monitoring requires a separate license and must be enabled before it is available for use.

For information about licensing, including a description of the types of licenses, Lite and Pro, see Browser RUM Licenses.

For information on enabling or disabling Browser RUM, see Enable and Disable Browser RUM.