Change component's log level
The article describes necessary steps to change a log level type between default prod (WARN/ERROR) and dev (DEBUG/INFO) for a specific server or component.
Make sure to run these steps as the runtime user (as defined in the wf_user variable in config.yml).
Log in via SSH to server where the component is installed. For the list of components and their location, refer to Product architecture.
Supported servers include APP, DB, OCR, ML, APM (Linux only). Log level type cannot be modified for RPA and BI servers.
Change a user to the default user
wfuser. Change a directory toPACKAGE_DIR.su - wfuser cd /opt/workfusion/wf_installer/If this directory is not present, it means that the installer was either deleted or unpacked to a different location.
Update the
log_level_typevariable with prod or dev value inconfig.ymllocated inPACKAGE_DIR.vi config.yml log_level_type: prod # possible values 'prod' or 'dev'The
log_level_typevariable allows to switch a log level for specific SPA components, prod is less verbose than dev. Check thelog_configvariable for details ingroup_vars/all/main.yml.Update the log level running the command with appropriate options. There are two valid scenarios to follow.
- Update log level for all components on the current server. In this case, you need to specify a server role (e.g.,
appas the server role in the example below).
./install.sh update_log_level app- Update log level for a specific component on the current server. In this case, you need to specify both a current server role and a component name (e.g.,
ocras the server role andocr-workeras the component name in the example below).
./install.sh update_log_level ocr -e log_components="ocr-worker"There can be one or more comma-separated component names in the
log_componentsvariable.- Update log level for all components on the current server. In this case, you need to specify a server role (e.g.,