Understanding Real User Monitoring (RUM)

Real User Monitoring (RUM) gives you visibility into the front-end performance of a web application and accurate insight into end-user experience. RUM visualizes application interaction patterns and provides an in-depth understanding of problems affecting real users accessing websites and applications in real time. You also get to analyze application performance from every aspect, like browser, platform, geography, ISP, and more.

For an in-depth understanding of Site24x7 RUM, along with the architecture, check out our getting started page.

How does it work?

Users just have to incorporate the provided JavaScript snippet into the header or footer part of the HTML code of the web application that needs to be tracked. From there on, all the performance data would be captured and presented in the Site24x7 client.

Site24x7 Real User Monitoring is compatible with popular browsers such as Chrome, Firefox, Safari, and Opera for monitoring web applications. Additionally, it offers support for monitoring webpages developed using Single Page Application (SPA) frameworks like Angular, Ember, and React.

RUM dashboard and configurations

APM Insight - RUM integration

Get a comprehensive view of an application's performance, user interactions, response times, and backend processing in a single console.

Integration of APM Insight and RUM

Features

Gain insights on performance and optimize real user experience with Real User Monitoring (RUM).

Troubleshooting

All troubleshooting practises are explained in this manual.

RUM troubleshooting tips

Best practices

Refer to our best practices document for valuable tips to enhance your monitoring experience.

Best practices for Real User Monitoring (RUM)

Licensing

RUM licensing is based on Pageviews. Site24x7 includes RUM in all the plans available. The number of Pageviews and Sites provided differs based on the plan.

Refer to this page for more details.

The initial page loaded by a Web browser and the HTTP calls in traditional applications (Track Ajax call/ Cross Ajax call is enabled) are currently considered a Pageview, regardless of the number of resources loaded behind the scenes. Pageviews are only counted for the webpage that the user visits, not for individual resources like images or CSS. If a user views the same page multiple times or refreshes it, each view is counted as a separate Pageview.