Lost? RUM comes to the rescue!

Knowing your end users location is important when monitoring your business critical applications.  

HP Real User Monitor (RUM) solutions (Mobile, Browser, and the traditional RUM network solution) uses the client IP address for location resolution. Then, a geo-location database is used to match the client IP address with a location.

 

In the image below you will see real end user data that was gathered from the HP Discover Mobile Application at the HP Discover (June 2014) in Las Vegas.

report

 

The Performance overview displays the locations with the slowest response time:

 The geo map provides an indication of the mobile application users along with a volume and status indication. A red icon indicates users experiencing performance problems and a bigger icon means a larger number of users. The location’s tooltip shows the overall number of sessions along with the average response time.

 

The table on the right displays the 10 worst performing locations.

 

Selecting specific location will filter the rest of the report components to help you determine whether the problem has unique characteristics. For example – is it specific to requests sent to certain domain or using a certain carrier?

 

We can see in the image that RUM detects the locations all over the world in which users were using this mobile application prior and during the event. Although most of the data seems to come from Las Vegas area, some of the data is being detected as coming from other locations due to the usage of the application by the users in their home location prior to the arrival to Vegas.

It is very easy to spot the red icons indicating that the users from that specific location had experienced slow performance (according to the threshold configured for the location) and the way to triage application issues and then solve them becomes easier and faster.

 

The translation of Client IP addresses to location usually gives good results. In addition, BSM gives you the ability to determine the location of an IP address, in cases where the automatic translation is not optimal:

  • IP addresses are automatically associated with a broad geographic area (e.g., a city, or a state). You may want to narrow the association to specific area.
  • Using roaming might give you the IP of your origin country while physically being in a different state.
  • By default, Intranet IP address’ do not have a mapping (due to the fact that it’s an internal IP and multiple organizations can use the same IP).
  • IPv6 client IP’s are not automatically mapped to a location.
  • Small percent of IP’s are not commonly used thus are not mapped.

Most of the above issues can be easily solved by manually tweaking the locations mapping. To learn all about it see Asaf Shechter’ s blog

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation