Skip to main content

The Traces Debug mode

In the Traces Debug mode, Talend Studio provides the capability to monitor the data row-by-row as it flows between different components in a subJob. You can choose to activate or deactivate Traces or decide what processed columns to display in the traces table that displays on the design workspace when launching the current Job. You can either choose to monitor the whole data processing or monitor the data processing row-by-row or at a certain breakpoint.

Information noteNote: The Job concerned in the following steps is for demonstration only. You can debug your own Jobs in the same way.
To debug the Job in the Traces Debug mode:
  1. With your Job open in Talend Studio, open the Run view and then select Debug Run.
  2. Click the Traces Debug button. The Job runs, with row content displayed under each main > row link.
    Information noteNote: Click the triangle in the right part of the button and select Traces Debug if Traces Debug does not appear on the button.
You can watch the content of the rows as they flow through the subJob until it encounters an error.
If an error occurs because of bad data, you can examine the values of each field in the row that caused the error. In this case, the error reported is a null pointer exception, as shown below.
Using the Traces Debug View, you can see that the null value in the Amount2 field probably caused the error.

This is an excellent way of debugging Jobs when you are working with a small sample of data. However, debugging Jobs that handle large volumes of data in this mode is not recommended because displaying every row visually in the Studio console can slow down the execution of the Job. In this case, you can try the Java Debug mode.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!