Appian is made up of multiple components, all of which must remain healthy for the platform to function properly. Traditionally, checking the health of each component requires running separate built-in scripts, which can be time consuming. Troubleshooting often involves collecting various log files based on the issue at hand - a process that typically requires manually identifying, zipping, and compressing multiple files and folders across different components.
This article introduces the following tools that simplify and streamline this process:
Table of Contents:
Appian Support maintains two scripts for log generation for non-containerized Appian (running on Windows or Linux OS):
logs/
service-manager
search-server
data-server
Note that the script only gathers the logs from the server that the script is run on. The script should be run individually on each server that the logs should be fetched from.
The Appian Diagnostics script appian_health_diagnostics.sh combines the different diagnostic scripts into a single script so that the state of each component in the environment can be understood by running one single script. In addition to the health of the Appian components the script also provides system level details like the RAM, CPU and disk usage of the server used to host Appian.
Note that this script does not interact with log files or retrieves any information that could be deemed sensitive in nature, apart from server hostnames. The script only leverages the existing out-of-the-box diagnostic scripts and prints the output to a new log file. The script only gathers the details of the Appian components which are hosted on the server that the script is run on.
In addition to the above scripts, Appian Support also maintains one script for both log generation and diagnostics for Appian on Kubernetes.
The script to gather engine, service-manager, kafka, and zookeeper logs can be downloaded here.
The script to gather tomcat, search-server, and Appian data-server logs can be downloaded here.
Run the following steps to execute the script:
<
APPIAN_HOME>
/logs
APPIAN_HOME>/shared-logs/*server_name*
<APPIAN_HOME>/shared-logs/machine1.example.com/
chmod +x appian_tomcat_ss_ads_log_generator.sh
./appian_tomcat_ss_ads_log_generator.sh
chmod +x appian_health_diagnostics.sh
appian_health_diagnostics.sh
-d *APPIAN_HOME* -p *SERVICE_MANAGER_PASSWORD*
./appian_health_diagnostics.sh -d /usr/local/appian/ae -p password
APPIAN_HOME/logs
The script to gather logs and metrics for Appian on Kubernetes can be downloaded here.
Run the following steps to execute the script
kubectl
chmod +x aok_log_diagnostic_script.sh
./aok_log_diagnostic_script.sh *my-appian-site*
./aok_log_diagnostic_script.sh *my-appian-site* 3
This article applies to Appian 18.3 and later.
Last Reviewed: May 2025