UEM, or User Experience Monitoring, has been a feature since FusionReactor 5.0.0. This feature allows you to monitor the experience of your users, by getting data on how long the request took to render on the users browser and how long the request took to transfer to the client machine, over the network. This data is visible on the requests as a sub transaction. There is also an overview of this data on the User Experience page.
The image above shows the UEM graph from a live server on the User Experience page.
How UEM works
How to use UEM
Here is the quick guide to get you started with UEM
To use UEM in a web page all that is needed is the inclusion of a call to the FusionReactor API (FRAPI) method getUemTrackingScript. (For examples please see UEM Script Usage Examples)
If you are using IIS or Apache with a connector to your application server, it will be required that you specify the ISAPI connector filer as the UEM Endpoint Filter in the UEM Settings page. (see Using FusionReactor via an external web server)
Information regarding the UEM Cookie
UEM requires the use of a cookie which is sent with all web requests to track the users page performance. It may be necessary to document that this cookie exists and is used for tracking performance. In order to comply with EU Legislation - see http://www.cookielaw.org/the-cookie-law/ - you 'may' be required to provide information to your users regarding what the cookie is used for, and then ask for consent from users for the right to store and retrieve information from their computer, tablet, or smartphone.