Experience monitoring provides you insight into how web applications are performing from a user’s perspective. It does this using a browser located on the monitoring point running scripts that emulate the workflow of a typical user. These scripts are run at regular intervals on a continuous basis from Enterprise Monitoring Points strategically located on your network and/or from Global Monitoring Points located around the world. Each time a script is run, the monitoring point measures the amount of time taken by the browser, the network, and the server running the application. It also breaks down the measurements by milestone within the script. All measurements are sent back to APM for analysis and presentation. In addition, you can set alerts that notify you whenever application performance is outside of acceptable limits.

Because the scripts are run from monitoring points at various user locations against the same applications your users are running, and generate network traffic in the same way users do, the monitoring results accurately reflect the application performance experienced by your users at those locations. Because the scripts are run at regular intervals, the results show how application performance changes over time. Performance-affecting changes made to the network, to the servers running the applications, or to the applications themselves, are easily identified within APM.

Setting up Experience monitoring involves specifying which monitoring points are going to monitor a given web application and creating a script to interact with the application. The unique combination of monitoring point, web application (referred to as the target), and workflow (which contains the script, its associated variables, alert settings, and Apdex settings) is known as a web path. The set of web paths associated with a given web application are grouped together in a web app group. Each time a script is run against a web application it is known as a web test.

Related topics: