| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Aborted_trans
|
The number of transactions that were aborted during the last measurement period |
Number
|
A high value indicates a bottleneck on the COM+ server.
|
| Aborted_trans_rate
|
The rate at which the transactions on an COM+
server aborted during the last measurement period
|
Trans/Sec
|
|
| Active_trans
|
The number of transactions
that are currently active
|
Number
|
A high value for this measure may indicate a large number of active transactions. Alternatively, this may also indicate that due to some reasons the users are not able to complete the
transactions.
|
| Max_active_trans
|
The high watermark of active transactions during the last measurement period
|
Number
|
|
| Committed_trans
|
The number of transactions that were committed during the last measurement period
|
Number
|
|
| Committed_trans_rate
|
The rate at which transactions were committed during the last measurement period
|
Trans/Sec
|
|
| Force_aborted_trans
|
The number of transactions that were forcefully aborted during the last measurement period
|
Number
|
|
| Force_committed_trans
|
The number of transactions that were forcefully committed during the last measurement period
|
Number
|
|
| In_doubt_trans
|
The number of transactions in doubt
|
Number
|
|
| Avg_resp_time
|
The average time taken by the COM+ Server to respond to user requests
|
Secs
|
A high response time denotes poor responsiveness of the COM+ server. This could be due to the server being overloaded or misconfigured.
|
| Max_resp_time
|
The maximum response time
|
Secs
|
|
| Min_resp_time
| The minimum response time
|
Secs
|
|
| Total_trans_rate
| The number of transactions per second
|
Trans/Sec
|
The high value of this metric indicates a lot of transactional activity happening on the server.
|