The Application Details dashboard shows the aggregated status of the selected application.
To access it, click an application pane in the Applications dashboard.
Listed below the Application Header are the detailed Business Transaction Splittings that constitute the application. The Business Transaction Splittings are sorted by priority. Favorite Business Transactions are always on top of the list. Next come Business Transactions with violations. See Ranking for more information.
This page explains how to use the Application Details dashboard to analyze performance problems. See Identify Problems in your Application for more information.
The application header shows the status of your application in the same way, as the Applications dashboard.
Reset base line for this application
Use this configuration function if the data of the last week does not make a useful baseline. This may be the case, for example, if severe problems occurred in the last week, or after deployment of new versions of applications that are known to have different response times.
To reset the baseline, click the gear icon and select Reset Base Lines for this Application, then click OK in the confirmation message. The baselines for all Business Transactions of the application reset and a new baseline is built from new data.
Resetting the baseline cannot be undone. Building a new baseline may take several hours, depending on the throughput.
Business Transaction splittings
By default, the Business Transaction Web Page Requests is monitored. This Business Transaction is split by URI parts and application.
To give you the best picture of how your applications and processes are doing and to alert you to problems as quickly as possible, Application Details are sorted by failure rate, response time, and by either process time or throughput, depending on which is more significant.
If you want to configure which Business Transactions to monitor, see Select Monitored Business Transactions.
Business Transaction splitting and Business Transaction
For Business Transaction Splittings, there may also be an ellipsis placeholder (...). This placeholder is used for all paths of the Business Transaction that do not constitute a splitting by themselves. Usually, these URIs do not meet the default condition of having a frequency of at least 5%.
Click the Business Transaction Splitting name to open the Business Transaction Details dashboard.
When the Business Transaction does not receive any data, the whole section is disabled and no further drilldowns can be performed.
You can use the star button on the left side of the header to define favorite Business Transaction Splittings and Business Transactions. Favorite Business Transaction Splittings are listed on top of the list. See Ranking.
Favorites are stored per user. Different users within the AppMon deployment may have different sets of favorites.
The chart shows the throughput count (requests per minute, blue line) and the expected range (green area), based on the data for the last week.
Throughput influences the failure rate and response time measurements: if the throughput is higher, the statistical spread for the failure rate and response time is smaller. See Application Overview Home - Throughput for more information.
Click the Throughput section to open the Business Transaction Details dashboard, focused on the throughput for its main chart.
The Failure Rate chart shows the failure rate trend (blue), baseline (green) and violations (red area). A violation is indicated if this Business Transaction currently produces more failures than expected, based on the data of the last week.
The number above the chart is the actual failure rate for this Business Transaction in the last 2 minutes. If there has been no activity in the last 2 minutes, a dash ( ‐% ) is shown.
Click the Failure Rate section to open the Business Transaction Details dashboard, focused on the Failure Rate for its main chart.
See Baseline and Smart Alerting Explained - Failure rate for more information on how Failure Rate is calculated.
The Response Times chart shows the median response time and response time of the slowest 10%.
The median response time is the typical response time (50% of requests have a slower response time and 50% have an equal or faster response time).
The response time of the slowest 10% represents the outliers (10% of requests have a slower response time and 90% have an equal or faster response time).
The numbers above the chart are the actual response times for this Business Transaction in the last 2 minutes. If there has been no activity in the last 2 minutes, a dash ( ‐ ms ) is shown.
A violation is indicated if either the median or the slowest 10% response time for this Business Transaction is higher than expected.
Click the Response Time section to open the Business Transaction Details dashboard, focused on the Response Time for its main chart.
See Baseline and Smart Alerting Explained - Response Time for more information on how response time is calculated.
The System Health section lists the health status of the hosts and processes that are used by this Business Transaction.
Processes are affected if they are unhealthy or running on unhealthy hosts.
You can also access the Transaction Flow for a single Business Transaction.
See Application Overview Home - System Health and Identify Problems in your Application - Analyze Transaction Flow and Host Health for more information.
Select monitored Business Transactions
This functionality is only available for users with administrative rights.
To include Business Transactions in the Application Monitoring or exclude them, click gear icon and select Select monitored Business Transactions.
The dialog box lists all available Business Transactions of the target System Profile. Business Transactions can be monitored only if they are split by Application and not more than one additional Splitting and are not split by Agent. Visit-based Business Transactions are not available for monitoring.
Select the check box to select a Business Transaction for monitoring; clear the check box to exclude it from monitoring.
All applications within the target System Profile are affected by the changes: selected Business Transactions are monitored for all applications of the target System Profile.
A dimmed Business Transaction is not available for the monitoring at the Application details dashboard. There are three possible reasons why it is unavailable:
- It is not split by Application at all.
- It is split by Application and more than one other measure.
- It is split by Agent
If it is not split by Application, you have to add the Application Splitting to the Business Transaction to make it available. If it is split by Application and more than one other measure, you have to remove the additional Splittings of the Business Transaction. If it is split by Agent you have to remove the Agent splitting. To make either change, click Manage Business Transactions in the Monitored Business Transactions dialog box.
See System Profile - Business Transactions for more information.
If you do not want changes to the Business Transaction to affect other applications, copy the Business Transaction and make your changes to the copy.
When you select a Business Transaction for the Application Details dashboard, the Failure Rates, Response Time and Count check boxes from the Business Transaction properties are selected automatically. These selections are needed for Application Monitoring.
If either check box is unselected, the Business Transaction is removed from the Application Overview. To include it again, select the Business Transaction again in the Monitored Business Transactions dialog box.
Business Transaction Splittings are listed in Application Details in order of relevance. A Business Transaction Splitting becomes more relevant if it signals abnormalities (failure rate violation, response time violation, or unhealthy processes) or has a higher throughput than other applications. Your favorite Business Transaction Splittings are listed first, and then the other splittings are listed according to the criteria in the following table. If a ranking criterion provides no measurable difference, the next criterion is considered.
|1||Splitting favorite||Favorite splittings are listed first.|
|2||Failure rate violation||Splittings with an active failure rate baseline violation are ranked higher.|
|3||Response time violation||Splittings with an active response time baseline violation are ranked higher.|
|4||Process health||Splittings are ranked by the number of unhealthy contributing processes.|
|5||Throughput||Splittings are ranked by average throughput value, or by the average throughput baseline value if it is available and is higher than the average throughput value.|
|6||Failure rate||Splittings are ranked by the current failure rate value.|
|7||Response time||Splittings are ranked by the current response time value.|
|8||Splitting Name||Splittings with equal rankings are sorted by name, ascending.|