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:
To hide the Global SLA settings, click the icon.
Click the Synthetic tab.
The Execution Plans that are defined for the application are listed:
|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.
From the Application Configuration screen, you can view details of all the transactions executed by an individual Execution Plan in the last 15 minutes. This allows you to easily see the results of any changes you make to an Execution Plan.
Transactions executed in the last 15 minutes are displayed at the bottom of the screen.
The data displayed in the table is refreshed automatically every minute. To temporarily disable the refresh, deselect the Auto Refresh checkbox. Deselecting Auto Refresh does not effect the view in the future. Subsequent views of recent executions will have Auto Refresh enabled.
The following details are displayed:
|Transaction Start Time|
Start time of the transaction
Name of the transaction
|Location||Location associated with the transaction|
|Latency||Amount of time (in milliseconds) the transaction took for completion from end to end|
Number of availability errors in the transaction
Availability errors occur when the application does not respond, or when the application responds with an error that indicates it is unavailable.
Number of accuracy errors in the transaction
Accuracy is calculated with the assumption that monitored applications are working as designed and that the information transmitted to clients is correct. Functions that can be evaluated to determine accuracy include link checking, content validation, title validation, and response data verification.
Number of execution errors in the transaction (unlikely to exceed 1)
An execution error indicates that there were problems with the script execution. It does not indicate anything about the health of the application.
|Execution Start Time|
Start time of this execution