Edit

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 wf_user variable in config.yml).

Log in via SSH to server where 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 user

Change user to default user wfuser.

Change directory to PACKAGE_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 different location.### Update log_level_type variable with prod or dev value in config.yml (located in PACKAGE_DIR)

vi config.yml

log_level_type: prod ## possible values 'prod' or 'dev'

log_level_type variable allows to switch a log level for specific SPA components, prod is less verbose than dev.Check log_config variable for details in group_vars/all/main.yml### Update log level running command with appropriate options

There are two valid scenarios to follow.

1. Update log level for all components on the current server. In this case, you need to specify a server role (e.g., app as the server role in the example below). See Server roles description for more information.

   ./install.sh update_log_level app
   

2. 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., ocr as the server role and ocr-worker as 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 log_components variable. Supported values are as follows:

• allocr

• workerocr

• restocr

• tasks

• qc

• wfbi

• wfagent

• workspace

• workfusion

• vds