In the following some ideas are given in order to proceed with the work of monitoring the end user experience. The Javascript file which captures the timings on the browser's side is called JS-File.

...

• The hook in the inspectIT Agent for inserting the JavaScript file does not work with all Application Servers. Especially, if static content ( for example static html files) is requested, the hook does not fire at all. Here, a more generic solution must be found. However, for development and testing purposes, JBoss 6.2 or Tomcat 7 works
  • testing of configuration parameters and their dependencies
• We need  exhaustive test cases for the JS-File which are tricky to implement. I would suggest to check the sessionStorage for correct results after simulating different user interactions.
• The function getDomPath does not always deliver correct results.
• A big problem is the Correlation ID: How to map the server ID with the user-action ID ?:
  • Approach: Use Cookies where the current User-Action ID is stored. For every user-request (sync and async), the ID will be sent to in the Cookie-Header to the server. 
    • Setting a new header field does not work because they can only be customized in case of Ajax requests, not for synchronous requests. 
    • Does this approach work reliably ? Testing is needed...
• RessourceTiming does not seem to work anymorefor async requests. Probably, Chrome API changed ?

Further Steps

The JS-File sends the gathered data back to the server. However, these data are currently only printed on the console. However, the measured data must be send from the server to the CMR where they should be displayed in the UI.