| 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 export script outputs the contents of the transaction log in a machine-readable format for analysis by Appian Support.
Run this script when directed to do so by Appian Support as part of troubleshooting.
LocationCopy link to clipboard
<APPIAN_HOME>/services/bin/export.sh (.bat)
OptionsCopy link to clipboard
| Short Name | Long Name | Required | Meaning |
|---|---|---|---|
| -h | --help | No | Show usage information |
| -f | --from-transaction | No | Id of the first transaction to export (inclusive) |
| -o | --output-directory | No | Directory to write the export file to |
| -r | --raw | No | Export the entire transaction log in raw kafka data format |
| -t | --to-transaction | No | Id of the last transaction to export (inclusive) |
Although none of the options are required, you must use either --from-transaction and --to-transaction to specify a transaction range or use the --raw option.
UsageCopy link to clipboard
The export script takes as a parameter the name of a service for which to export transactions. One of: analytics00, analytics01, analytics02, channels, content, download-stats, execution00, execution01, execution02, forums, groups, notifications, notifications-email, portal, process-design.
1
export.sh groups --from-transaction 1 --to-transaction 100
Copy