During execution from the command line, Silk Test Workbench logs events into .LOG files in the directory %LOCALAPPDATA%\silk\silktest\logs. By default, the logging level is set to info and each execution of a command-line executable creates a new log file that contains the PID, the date, and the time in the filename. Subsequent executions of the same program delete old files and create new ones.

The following table provides a filename example for some command-line executables:

Program Example Filename
SilkTest.exe SilkTest(Pid=25184)_20171030_1635.log
STW.exe STW(Pid=13204)_20171031_0839.log
STWDBConfig.exe STWDBConfig(Pid=32924)_20171030_1635.log
STWExport.exe STWExport(Pid=32560)_20171030_1635.log
STWImport.exe STWImport(Pid=26640)_20171030_1635.log
STWMaint.exe STWMaint(Pid=13488)_20171030_1618.log
STWPurge.exe STWPurge(Pid=30096)_20171030_1635.log

You can set your logging preferences by modifying the file workbench.properties in the gui folder of your Silk Test Workbench installation. By default, this folder should be located under C:\Program Files (x86)\Silk\SilkTest\ng\gui. In this file, you can specify the log level, the log style, the log directory, and so on.

For example, if you require multiple log files to be created for a single program, change the setting nativeLog.clearPerProcessLogs to 0 so that the files are not deleted.

Additionally, you can change the setting nativeLog.LogPerProcess to 0 to change the way files are created. In this case all executable files write to a single file named silktest.log.
Note: The logger attempts to recreate the file for each execution unless nativeLog.OverWriteExisting is set to 0.