<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1194005000700189&amp;ev=PageView&amp;noscript=1">

From Vizuri's Experts

End User Experience Monitoring - Use It or 'Lose' It - Part 4

This is part 4 in a series on End User Experience Monitoring - Use it or ‘Lose' it.

In part 3 of this series, we have seen who gains the most from End User Monitoring (EUM)? and What benefits do they get from using EUM? In this part of the series, we will explore several different views of EUM and briefly discuss the advantages of analysing these views to drill down to the root cause of poor end user experience. 

End User Monitoring (EUM) Views

EUM dashboard provides us access to multiple views/panels to determine the root cause for poor end user experience.

Each category of views provides slightly different perspective into what’s happening with the end user. These are broken down into:

Geographical view

Web Page view

Browser/Device view

Geographical View

The geographic view reports EUM data by geographic location. You can use this view to learn about which regions have the highest loads, longest response times and most errors.




Figure 5: Geographical view displays geographic distribution on a map or a grid

Web Page View

The web page view reports EUM data by a web page which further breaks down into three categories

Page - Represents what an end user sees in a single browser window

IFrame - Represents a page embedded into another page

Ajax Request - Represents a request for data sent from a page using ajax


Figure 6: Web page view displays the EUM data by web page


With base page view you can also access the snapshots captured for individual pages to further drill down into the root cause of a problem as shown in the figure below


Figure 7: Web page view also displays the list of snapshots captured for individual pages


The browser and device view reports the EUM data by listing the type of browser, the browser version and the type of device the end user is using to access your application. Monitoring this view help us learn which browsers, browser versions and devices are having performance problems so that we can troubleshoot them accordingly.



Figure 8: Overall Distribution chart showing the percentages of your end users using different devices.

One might think why do we need all these different views? Why can’t we have just one screen covers all the performance issues of my end users?

A key reason to have these separate views is that a performance problem that may appear in one view may or may not be visible in other views. In other words, each view emphasizes different aspects of EUM and not all views share the same information. For eg., If a user is experiencing very poor performance on one of the most infrequently accessed page of your application, then the overall performance change may not be obvious and the summary key performance indicator may falsely represent that your application is behaving normally.

Stay tuned for our last segment in this five part series to find out what’s in the Cloud for EUM. In the final segment, we will take a peek at the EUM Cloud Service capabilities and discuss how we could use it as a highly scalable platform for processing end user requests and for performing data analysis.

Anil Mirge

A former Vizuri developer, Anil Mirge brought more than six years of working experience in all phases of software design and development to the Vizuri team. Interested in this post? Connect with our team of experts by