Monitoring synthetic transactions by execution
For applications with synthetic transaction monitoring enabled and as the application operator, you can use the Executions view under the Application View tab to see information about executions, down to the transactions level, for a specific location and the selected time frame. By default, transactions are sorted by start time. To find the information you need, you can sort by any of the columns in the table. The time range of the data displayed in the Executions view is initially the same as the time range from the Locations view. You can change the displayed time range.
Before you begin
Before you can diagnose and resolve performance and availability problems with your synthetic transactions in an application, ensure that your system meets the following conditions:
- Synthetic transaction monitoring is set up with synthetic SLA events enabled, usually by an application specialist in your organization.
- You are logged in with -level access, or higher, so that you have access to the Application View tab.
To open the Executions view
- From the navigation pane in the TrueSight console , select Monitoring > Applications.
- Select one application that you want to examine in detail.
- From the Application View tab, click the Synthetic Tier icon.
The tier members are shown aggregated by status.
- Select one or more statuses to see the list of the Execution Plans.
The Execution Plan names are displayed.
- Select one or more Execution plans to see more details for those Execution Plans.
- Click the action menu for an Execution Plan and select Show Locations.
- In the Application View > Locations view, click the action menu of the location that you want to investigate.
- Select Show Executions.
The Application View > Locations > Executions view is displayed.
The Executions view is limited to the last 250 executions.
To locate a specific execution if you have a large volume of executions, use a smaller custom time range.
The following details are displayed in the Executions view:
|Transaction Start Time|
Start time of the transaction
Name of 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
Transaction drill-down menu
Click the action menu of a transaction to access the menu for that transaction. The following actions are available:
|Download Execution Log|
Downloads the Execution Log for the execution.
|Custom Timers||Displays all custom timers defined for this transaction and their latency.|
Displays all page timers defined for this transaction and their latency.
|Error Messages||Displays all error messages issued for this transaction.|
To view custom timers
Click the action menu of the transaction and select Custom Timers.
A window opens displaying all of the custom timers defined for the transaction and their latency (in milliseconds).
To view page timers
Click the action menu for the transaction and select Page Timers.
A window opens displaying all of the page timers for the transaction and their latency (in milliseconds).
To view error messages
Click the action menu for the transaction and select Error Messages.
The View Errors window opens displaying all of the error messages received while running the transaction. The error messages are sorted by category (Availability, Accuracy, and Execution).