How to enable additional logging for Talend Studio or CommandLine

Talend Version          6.0.1


This article provides details on enabling additional logging for Talend Studio and CommandLine using the talendDebug parameter.
Additional Versions 6.1.1, 5.6.2
Key words talenddebug, logging, studio, debug, log, verbose
Product Talend Data Integration
Component Studio
Article Type Logging
Problem Description Log information available on Talend Studio or CommandLine may sometimes be insufficient when troubleshooting some issues. The log file from Studio|CommandLine Home/workspace-directory/.metadata may not always have the level of detail that may be needed.
Problem root cause Debug level information from Talend Studio / CommandLine is limited by default.
Solution or Workaround

The workaround is to use the --talendDebug parameter when starting the Talend Studio or CommandLine.

In the case of Talend Studio, the application can be started from the command line with the additional --talendDebug parameter. For example, on Windows, the command to start the application in debug mode from the Studio-Home directory would be:

Talend-Studio-win-x86_64.exe --talendDebug > debugLog.txt

This would create the log file debugLog.txt with the necessary log information in debug mode. The command above could be saved to a script and used for launching the Talend Studio in this mode.

Enabling debug level logging for CommandLine can be accomplished by editing the script used to start CommandLine. Below is an example showing how the script can be edited to enable this logging for the Linux version of the CommandLine script:

./Talend-Studio-linux-gtk-x86_64 -nosplash -application org.talend.commandline.CommandLine -consoleLog -data commandline-workspace startServer -p 8002 --talendDebug > debugLog.txt


  • The debugLog.txt file will be verbose and its size may increase rapidly. Remove the --talendDebug parameter once the troubleshooting is done.
  • Errors may be seen in Job Conductor due to this additional debug parameter, even with successful generation. This is normal.
JIRA ticket number  
Version history
Revision #:
4 of 4
Last update:
‎07-07-2017 06:46 PM
Updated by:
Labels (1)
Tags (1)