Monitoring synthetic transactions in the Locations view
In the Locations view, you can see aggregated data of a specific Execution Plan based on its 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.
Default value is Last 5 Minutes.
To open the Locations view
- In the Application View, click the Synthetic Tier icon the Locations view.
The Execution Plans are displayed. - Click on the action menu for an Execution Plan and select Show Locations.
The Locations view is displayed.
The following details are displayed in the Locations view:
Column | Description |
|---|---|
Location | Logical grouping of Synthetic TEA agents. The grouping is usually based on geographical location. |
Application | Application to which this Execution Plan is assigned |
Execution Plan | Execution Plan being monitored |
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 |
Availability Errors | 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. |
Accuracy Errors | 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 |
Execution Errors | 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-in-the-Executions-view.
Related topics
Monitoring-synthetic-transactions-to-predict-application-health