Download PDF
Download page Monitor the Performance of Business Transactions.
Monitor the Performance of Business Transactions
After verifying and refining your business transaction scheme, you can focus on monitoring the business transaction performance. The monitoring and troubleshooting tools within the Controller UI provide a business transaction-oriented view of performance. For example, transaction snapshots tie together all the code call graphs across the monitored tiers that participate in processing a particular instance of a business transaction.
The business transaction list contains a high-level view of business application performance by a transaction. You can click a particular business transaction to access additional information on the business transaction, such as information on slow performing instances of this transaction, errors, and the transaction analysis view.
You can monitor the performance of business transactions with Splunk AppDynamics using:
View Transaction Scorecard to Monitor the Performance
The transaction scorecard summarizes the performance of a business transaction at the application, tier, or node level within a specified time range. It covers the number and percentage of business transaction instances (calls) that are normal, slow, very slow, stalled or errors based on the configured thresholds for these criteria.
The call counts in the scorecards in different dashboards indicate a different meaning:
- In the application dashboard, the business transaction health scorecard aggregates the metrics for all the completed business transactions in the application, including the default business transactions. The number of calls is based on the number of business transactions that are completed. The percentages for those calls are based on the average for all the completed business transactions in the application. For example, if the scorecard displays 3% for very slow transactions, on average 3% of the calls for completed business transactions in the application were slow.
- In a tier dashboard, the transaction scorecard aggregates the metrics for all the nodes in the tier. The number of calls is based on the number of requests that the tier handled, including continuing transactions, threads spawned, and so on.
- A node dashboard is similar to the tier dashboard in that it is based on the number of requests the node handled. The transaction scorecard displays the metrics for the single node.
- In a business transaction dashboard, the transaction scorecard displays the metrics for the entry point of a business transaction.
Transaction Score View
For a more detailed view of the performance of a transaction over time, navigate to the business transaction dashboard and click the Transaction Score tab.
The graph in the tab displays the user experience for the selected business transaction, showing its performance relative to the performance thresholds as a bar chart. For each time slot, the bar reflects the total calls, while the color segments green, yellow, and so on indicate the relative number of those calls that are normal, slow, very slow, stall, or errors.
The solid blue line in the graph indicates the average response time for the transaction over time, while the dotted line shows the baseline, if available.
Slow Database or Remote Service Calls
Splunk AppDynamics collects data about the performance of business transaction calls to the databases and remote servers from the instrumented app servers. You can drill down to the root cause of slow database and remote service calls.
- In the Controller UI, go to Business Transactions > Dashboard.
- In the dashboard, click a business transaction call and then click the Slowest DB & Remote Service Calls tab.
- Select a call from the list and click the View Snapshots link to show a list of correlated snapshots.
- Click the Exe Time (ms)
column to sort the transactions from slowest to fastest.
- Select a transaction and click Drill Down.
- Select a potential issue from the Potential Issues list.
- Click Drill Down in the flow map pane to see the complete set of call graph segments retained for this transaction.
- Review the Time (ms) column and select the transaction with the longest execution time for this method relative to the transaction execution time.