Setting up and managing synthetic transaction monitoring
After that are required for monitoring synthetic transactions and , you configure how to generate the synthetic transactions for monitoring from the App Visibility Manager.
You use the following features to set up the simulation of synthetic transactions:
Locations—Each synthetic TEA Agent is associated with a location, which is a logical group (such as by geographical location or application type), that is used for load balancing and high availability.
- Scripts—From the TEA Agents, scripts run sequences of instructions that simulate user transactions. App Visibility comes with the six prerecorded scripts. You can use an external scripting tool (Silk Performer) to create more scripts. For more details see the .
- Execution Plans—An Execution Plan is a wrapper for a script. Through an Execution Plan, you specify the configuration for the script (including custom attributes), locations on which the script runs, run schedules, and blackout periods. Every Execution Plan is associated with an application. You can modify or override some of the settings in the Execution Plan definition.
This section presents the following topics:
- Viewing an application's synthetic settings
- Using scripts to simulate end-user transactions
- Preparing Silk Test script execution for synthetic transaction monitoring
- Editing an application's synthetic settings
- Configuring and managing synthetic metric rules
- Daylight saving time and blackout periods
- Application and Execution Plan status
- Setting execution log retention levels
- Reclassifying Synthetic Monitor Execution errors and Accuracy errors as Availability errors
- Converting from Monitoring Policies to Synthetic Metric Rules
- Reclassifying Synthetic Monitor Accuracy, Execution, and Availability errors in TEA Agent