| Beginning with Appian 25.4, all new versions of Appian will require containers managed by Kubernetes to run in a self-managed environment. Review the 24.4 release notes and frequently asked questions to learn more. |
PurposeCopy link to clipboard
The Appian engines synchronously store write transactions in the Kafka component of the Internal Messaging Service as they are applied. For troubleshooting purposes it is sometimes useful to be able to look at the contents of the transaction log for an engine to see how many transactions were applied in a given time period, what types of transactions are flowing through the system, or what parameters were used in a particularly slow transaction. The transactionLogUtil script outputs the contents of the transaction log, including the timestamp, id, method name, executing user, size, and duration of each transaction.
Run this script when directed to do so by Appian Support as part of troubleshooting.
LocationCopy link to clipboard
<APPIAN_HOME>/services/bin/transactionLogUtil.sh (.bat)
OptionsCopy link to clipboard
| Short Name | Long Name | Required | Meaning |
|---|---|---|---|
| -h | --help | No | Show usage information |
| -s | --start | No | Starting date or transaction id |
| -e | --end | No | Ending date or transaction id |
| -l | --limit | No | Maximum number of transactions to process |
| -p | No | Print transactions |
The --print option requires a format of either detail, summary, or hex. The default value is summary.
Running without the --start, --limit, and --end parameters will result in all transactions for the specified service being printed out.
UsageCopy link to clipboard
The transactionLogUtil script takes as a parameter the name of a service for which to export transactions. One of: analytics00…analytics31, channels, content, download-stats, execution00…execution31, forums, groups, notifications, notifications-email, portal, process-design.
1
./transactionLogUtil.sh content
Copy