...
Per transaction stats collection can be enabled with the capturePerTransactionStats configuration property for an application, and configuring a dedicated binary transaction log using the perTransactionStatsLogging configuration element. Per transaction stats collection collects timestamps that are capture captured when recording message latency stats, ODS store latency stats and transaction latency stats, so those must be enabled as well to be included in per transaction stats. The DDL configuration block below shows a typical set of configuration for collecting all per transaction stats:
...
| Entry | transactionId | simpleClassName | transactionInSequenceNumber | TransactionOutSequenceNumbertransactionOutSequenceNumber |
|---|---|---|---|---|
| 1 | 1 | NewOrderMessage | 1 | 0 |
| 2 | 1 | NewOrderMessage | 2 | 0 |
| 3 | 2 | NewOrderMessage | 1 | 0 |
| 4 | 2 | NewOrderMessage | 2 | 0 |
...
| Entry | transactionId | simpleClassName | transactionInSequenceNumber | TransactionOutSequenceNumbertransactionOutSequenceNumber |
|---|---|---|---|---|
| 1 | 1 | NewOrderEventMessage | 1 | 1 |
| 2 | 1 | NewOrderAckMessage | 1 | 2 |
| 3 | 1 | NewOrderEventMessage | 2 | 3 |
| 4 | 1 | NewOrderAckMessage | 2 | 4 |
| 5 | 2 | NewOrderEventMessage | 1 | 1 |
| 6 | 2 | NewOrderAckMessage | 1 | 2 |
| 7 | 2 | NewOrderEventMessage | 2 | 3 |
| 8 | 2 | NewOrderAckMessage | 2 | 4 |
...