Use the Synthetic tier in the Application View to monitor the synthetic transactions of an application that are run by BMC Transaction Execution Adapter Agents (TEA Agents), measuring them against defined SLAs. The view helps you identify issues in the application and locate servers where you can begin investigating problems. You can examine and trend server metrics and correlate server issues with application-transaction issues. The Application View helps you diagnose and resolve performance and availability problems with your synthetic transactions to predict application health and user experience.
This topic contains the following sections:
From the Applications page, you evaluate the impact and severity of events for your applications. Select one application to closely examine problems in the Application View.
The Application View tab opens on the Application Monitoring page if the application was automatically detected by App Visibility. Otherwise, the Synthetic Health tab opens automatically (see Investigating application issues reported by synthetic health events for more details).
In the Application View, you can monitor the health and performance of an application that is monitored by TEA agents. If synthetic monitoring is activated for the application,the Synthetic tier icon (on the lower left side of the Application View) shows a summary of the synthetic executions within the selected time period.
Example of the Application View
From the Date action menu, select a specific date to display in the Application View.
Note
You can select any date, but data is displayed only if it falls within the retention period that you set when you installed App Visibility. Default is 30 days.
To change the retention period, see Changing App Visibility collector settings.
Click the Synthetic Tier, examine the Executions and problems, and then drill down to further diagnostic data.
Use the following instructions to drill down to detailed data for each Execution Plan.
Note
If an Execution Plan is deleted or deactivated, all problems related to the Execution Plan are automatically closed.
The color of the Execution Plan corresponds to the highest severity level breached by the executions of the Execution Plan. In other words, the color matches worst problem that the Execution Plan had during the time frame.
Select the Summary tab to see the following data:
Column | Description |
---|---|
Severity | Icon indicating the severity level of the Execution Plan |
Execution Plan Name | Name of the Execution Plan |
Executions | Number of Execution Plan executions that completed (or partially completed) in the time frame. Partially completed means that the Execution Plan includes multiple transactions but only some of the transactions completed in the defined time frame. |
Impacted Executions | Percentage of executions that had one or more errors. Errors can be any of the following:
Violations and errors are according to defined SLA thresholds. For details about metric rule violations, see Investigating application issues reported by synthetic health events. |
Latency Violations | Percentage of executions that exceeded the latency threshold, regardless of the defined SLA threshold |
Availability Errors | Percentage of executions that encountered availability errors, regardless of the defined SLA threshold |
Select the Problems tab to see the following data:
Column | Description |
---|---|
Severity | Icon indicating the severity level of the Execution Plan |
Problem | Type of problem encountered, which can be any of the following:
|
Execution Plan Name | Name of the Execution Plan |
Problem Started | Time and date when the problem which caused the event severity started If the problem started earlier than the displayed time, click the start time to reset the time selection. The time slider moves to the five-minute period that includes the problem start time. |
Threshold | Percentage configured in the SLA threshold |
Current Status | Possible statuses of the problem are as follows: Open—The problem is currently still occurring. Closed—The problem was resolved at the displayed time. |
The Locations view replaces the Application view data.
For more details about drilling down to synthetic member data, see Monitoring synthetic transactions by location and Monitoring synthetic transactions by execution.
Investigating problems with Web and Business tiers
Analyzing database problems with the Database tier
Setting up and managing synthetic transaction monitoring