Real User Monitoring (RUM) entails collecting performance data from your actual website users. Uptrends' regular synthetic monitoring runs in a predictable environment, using a fixed monitoring interval. Synthetic monitoring works well for availability monitoring and detecting performance changes of web pages. RUM, on the other hand, runs in less predictable environments (i.e. on your end user’s devices and computers) and as such focuses much more on measuring the actual experience of your users. We’ve placed your RUM-based data inside your existing Uptrends account, and you can see your RUM data and synthetic data side by side.
Getting started with Uptrends RUM
Starting with RUM entails two actions: adding a RUM website definition to your account, and implementing the script in your actual website.
Adding your first RUM website to your account
- If you’re not already using the Real User Monitoring function in Uptrends, you can try it for free by starting a RUM trial. In the Apps & Extras menu, click the Try Real User Monitoring option.
- On the Start RUM trial page, click the button.
- Fill in the URL of the website you want to monitor. Click the button.
- Your RUM trial has now started. Click the button to navigate to the settings of your new RUM website.
Adding additional RUM websites
After the initial setup is done, the RUM section on the menu will contain a Real users sub-section, where you can find the RUM-related dashboards and manage your RUM websites. To add additional RUM websites:
- Expand the RUM section in the menu.
- Click the + icon next to RUM websites.
- Fill out the Name for the website, and its URL.
- If your website is a single-page application (SPA), tick the option Use Single Page Application Tracking.
- In case the website uses URL fragments (e.g.
#fragmentat the end), and those are a significant part of your URLs, tick the Include URL fragment option. Doing so will prevent Real User Monitoring from discarding everything after the # symbol.
- After setting all options, click the button in the lower left.
- The script will now appear in the Implementation tab. The next chapter will cover implementing the script.
Implementing the script in your website
- Please make sure you have access to the code of your website, so the content of your pages can be changed.
<head>portion of your web pages. Placing the script inside the
<head>tags ensures that the script loads as early as possible. Early loading helps the monitor to capture as much of the appropriate timing data as possible.
- Ensure that the updated version of your website is accessible through the domain you specified in the URL field.
- RUM data will be tracked as soon as visitors are accessing your updated site. You should see data in the RUM overview dashboard right away, in real time.
Uptrends makes the RUM script and the components the script uses available to you under a BSD (Berkeley Software Distribution) license. You can find the full text at https://hit.uptrendsdata.com/license.txt.
One script per website
Keep in mind that each script is specifically for a single website since it contains a
sid which uniquely identifies the corresponding RUM website in your account. For each page view that Uptrends registers for a particular RUM website, we’ll verify that the page view is, in fact, coming from the website domain that you specified. Let’s take a look at an example of what we mean.
www.your-domain.com as an example website, by default, we allow page views to come from both
your-domain.com. If you also include the same script on a website hosted at
www.your-other-domain.com, RUM will not work on those other domains, for RUM doesn’t register page views originating from other domains. Each website needs a separate RUM instance to maintain sensible data.
Essentially, if you want to track real user monitoring data on more than one website, you need to treat them as separate RUM websites in Uptrends as well. For each website domain you wish to monitor, you’ll need to set up an additional RUM website, for each domain gets a different script.
The domain verification also means that RUM will only work in your real production environment. If you have separate development and test environments running locally or under a different domain, RUM will not register page views for those sites.