Monitoring synthetic transactions by location
For applications with synthetic transaction monitoring enabled and as the application operator, you can use the Locations view under the Application View tab to see aggregated data of a specific Execution Plan based on its locations.
Application View > Locations
The Locations view displays data for a specific time range. Time ranges are displayed relative to the current time based on the time set in your TrueSight console User Preferences.
For example, if Last 60 Minutes is selected, and it is now 8:00 A.M. based on the time in your console, synthetic executions that ran from 7:00 A.M. until now are displayed. The default value is Last 5 Minutes.
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 Locations 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.
- 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.
The Application View > Locations view is displayed.
The following details are displayed in the Locations view:
Logical grouping of Synthetic TEA Agent. The grouping is usually based on geographical location.
|Executed Transactions||Number of transactions performed during the selected time range for this location|
|Latency violations||Percentage of transactions that exceeded the latency threshold defined in the SLA|
Percentage of transactions that had Availability errors
Availability errors occur when the application does not respond, or when the application responds with an error that indicates it is unavailable. The availability rate provides information regarding whether the application is running and whether it provides basic responsiveness to client requests.
Percentage of transactions that had Accuracy errors
Accuracy rates are 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. If a monitoring script contains customized functions that are used to ascertain system accuracy, those functions are factored into the accuracy rate as well
Percentage of executions that had Execution errors
An execution error indicates that there were problems with the script execution. It does not indicate anything about the health of the application.
To drill down to the Executions view
Click the action menu for the location you want to view in more detail information. The details displayed in the Executions view are only for the specific location.
For more details about the Execution view, see Monitoring synthetic transactions by execution.