Introduction to scripting

Experience monitoring uses scripts, run on a browser located on the Monitoring Point, to simulate a typical user’s interactions with a web application. As a script proceeds, it measures the timing of responses from the application and forwards these measurements to APM. APM then creates a picture of the application performance from a user perspective and generates alerts when the measurements are outside an acceptable range. Alerts are also generated for issues such as connectivity loss, HTTP errors, and an Apdex value indicating unacceptable user satisfaction.

Scripts can be created either manually or by using a 3rd-party script recorder. In either case, they are divided into logical sections called “milestones”. Scripts run continuously on a periodic basis. When they run, they pass timing data for each milestone back to APM.

Two scripting languages are supported: Selenium and AppNeta. Some of the feature differences include:

Feature Selenium AppNeta Synthetic
Browser used Chrome Firefox
Industry standard Yes No
Continued enhancements Yes No

We recommend using Selenium if your Monitoring Point supports it. Currently Selenium is supported on all Global Monitoring Points as well as several Enterprise Monitoring Point models. See the Monitoring Point Feature Comparison page for details.

Analytics aware: Traffic generated by APM scripts does not affect analytics information gathered by Google Analytics, Fullstory, and

HTML elements only: APM supports interaction with HTML elements only. It does not support 3rd-party browser add-ons or multimedia players. This includes Flash, ActiveX, Java applets, browser extensions, and video/audio players.