To see synthetic settings for an application, you need to turn Synthetic on for the application and then configure the application accordingly. See Editing synthetic settings for an application for more details.
Synthetic configuration includes the following:
An Execution Plan provides the interface for a script and its execution. Through an Execution Plan, you specify configuration values for the script, indicate on which locations the script runs, and define the run schedule.
BMC Synthetic Transaction Execution Adapter (TEA) Agents can process up to 120 Execution Plans each.
This topic contains the following procedures:
For more details about the specific metrics, see Monitoring synthetic transactions in the Locations view and Monitoring synthetic transactions in the Executions view.
Note
To hide the Global SLA settings, click the icon.
Click the Synthetic tab.
The Execution Plans that are defined for the application are listed:
Column | Description |
---|---|
Name | Name of the Execution Plan This name is always unique within an application. It is possible for different applications to have Execution Plans with the same name. |
Status | Active or Inactive Place the mouse cursor over the word Inactive to see the reason for the Deactivation. Possible causes are:
For more details, see Application and Execution Plan status. |
SLA Settings | Custom or Global
|
Script Name | Name of the script used by the Execution Plan If the name ends with an ellipsis, the script name is too long to be displayed here. Place the cursor over the truncated script name to see the entire name. |
Locations | Number of locations in use by this Execution Plan Place the mouse cursor over the number of location to see the names of the individual locations. |
To sort the list based on a specific column, click the relevant column heading. To sort in reverse order, click the column heading again.
Editing an application's synthetic settings
Using scripts to simulate end-user transactions
Application and Execution Plan status
Daylight saving time and blackout periods
Preparing Silk Test script execution for synthetic transaction monitoring