tLogCatcher properties - 6.3

Talend Open Studio for Big Data Components Reference Guide

Talend Open Studio for Big Data
Data Governance
Data Quality and Preparation
Design and Development
Talend Studio

Component family

Logs & Errors

Basic settings

Schema and Edit Schema

A schema is a row description, it defines the fields to be processed and passed on to the next component.

The schema of this component is read-only. It describes the properties of the log data. You can click the [...] button next to Edit schema to view the predefined schema which contains the following fields:

  • moment: the time when the message is caught.

  • pid: the process ID of the Job.

  • root_pid: the root process ID.

  • father_pid: the father process ID.

  • project: the name of the project.

  • job: the name of the Job.

  • context: the context used to run the Job.

  • priority: the priority level of the message.

  • type: the type of the message.

  • origin: the name of the component that triggers the message.

  • message: the message content.

  • code: the error code level.


Catch Java Exception

Select this check box to trigger the tCatch function when a Java Exception occurs in the Job.


Catch tDie

Select this check box to trigger the tCatch function when a tDie component is called in a Job.


Catch tWarn

Select this check box to trigger the tCatch function when a tWarn component is called in a Job.

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio User Guide.


This component is usually used as the start component of a secondary Job which is automatically triggered at the end of the main Job.


If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide.

For more information on the log4j logging levels, see the Apache documentation at