A 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.
Slow and very slow transactions have completed. Stalled transactions never completed or timed out. Configurable thresholds define the level of performance for the slow, very slow and stalled categories. See Configure Thresholds.
Scorecards appear in many places in the UI, including the application, tier, node, and business transaction dashboards.
The call counts in the score cards in different dashboards have different meanings:
- 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 have 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 forth.
- 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 entry point to an instance of a business transaction.