All About the Apps
Showing results for 
Search instead for 
Do you mean 

Get real with HP Diagnostics and HP RUM

HPE-SW-Guest ‎04-07-2014 11:49 AM - edited ‎06-09-2015 01:03 PM

Guest post by Ketty Agiga, HP Software Engineering


Applications are often required to communicate with back-end servers; get the status of a user’s bank account, receive updates from friends, or post a new picture to a blog. Slowdowns in this communication impact your end users, but those slowdowns can’t always be traced to a backend issue.  There are various other factors which can affect application response times—network load, client type, location, user request sequence, etc , . Identifying slow response times and pinpointing the problem area is the first step in improving performance. It is also the first step to make your users happy.


Client Monitoring provides a real end-user perspective on application health. As users interact with your applications, performance and exception data is collected from all users’ browsers in near real time.


In this blog post I want to discuss the procedure of integrating HP Real User Monitor Client Monitoring (RUM CM) with HP Diagnostics for a nice and easy solution that saves the time of manual JavaScript injection into the relevant pages of the application.


  RUM CM and Diagnostics provide complementary perspectives for isolating performance issues:


  • RUM CM provides visualization of the end user experience across different dimensions such as locations, actions, external domains, errors, user groups, and so forth
  • Once an end user problem is detected, Diagnostics can provide contextual drilldown and additional information to further investigate server side issues.

In the following procedure I will explain how the integration works and show its main benefits.





 How does CM collect data?


Client Monitoring works by injecting JavaScript (clientmon.js) into the relevant pages of your application. Note that the JS would be injected to JSP pages automatically thanks to Diagnostics probe capabilities. For non-JSP pages (e.g. static HTML files) you’ll need to add the JS manually. As users are interacting with the application in the browser, the end user performance and exception metrics are captured and sent to RUM Client Monitor probe. The communication is tagged such that the backend activities could be automatically correlated with the end user requests. This allows you to drill down from a RUM report to a Diagnostics report and keep the same context.


To learn more see Diagnostics and RUM Integration guide (HP passport login required)



Outcome: View RUM-Diagnostics Monitored Data


Here is an example of RUM Report which displays Session Details of a monitored web application




To isolate performance issues we can Drill Down into the Session Details and further on into the Diagnostics details to see the specific Server Request down to the call stack.









Last note: 

In this blog post I presented the ability to combine RUM Client Monitoring with Diagnostics. Pairing those two products together provides end to end view of application performance from the end user to the backend.


If you would like more information on Diagnostics and RUM CM, here is some additional information:



About the Author


This account is for guest bloggers. The blog post will identify the blogger.

27 Feb - 2 March 2017
Barcelona | Fira Gran Via
Mobile World Congress 2017
Hewlett Packard Enterprise at Mobile World Congress 2017, Barcelona | Fira Gran Via Location: Hall 3, Booth 3E11
Read more
Each Month in 2017
Software Expert Days - 2017
Join us online to talk directly with our Software experts during online Expert Days. Find information here about past, current, and upcoming Expert Da...
Read more
View all