Error logging in Talend Studio

author
Rekha Sree
EnrichVersion
6.4
6.3
6.2
6.1
EnrichProdName
Talend Big Data
Talend Real-Time Big Data Platform
Talend Cloud
Talend MDM Platform
Talend Open Studio for Data Quality
Talend Open Studio for Data Integration
Talend Data Management Platform
Talend Open Studio for Big Data
Talend Open Studio for ESB
Talend Data Integration
Talend Data Fabric
Talend Data Services Platform
Talend Big Data Platform
Talend ESB
Talend Open Studio for MDM
task
Design and Development
EnrichPlatform
Talend Studio

Error logging in Talend Studio

This article describes the different types of logging provided by Talend Studio.

Overview

Talend performs three different types of logging:
  • Statistics, the Job execution statistics at the Job and component levels are logged
  • Error, the errors, warnings and exceptions at the Job level are logged
  • Meter Logging, the data flow inside the Job is logged
These three logging types can be configured at the following levels in Talend Studio:
  • Project settings
  • Components
  • Job settings
  • Job design
  • Log4j
  • Log Server

Error logging at the project level

This section explains how to set logging at the project level.
  1. Navigate to File > Edit project settings > Job settings.
  2. Select the check box below Stats and Logs to enable the logging at the project level.
    If logging at the project level is enabled, every new Job created inherits the settings.
  3. Configure the output of your logs by choosing one of the options below.

Error logging in the console

This section explains how to configure your project to display the logs in the console.
  1. Navigate to Job settings > Stats & Logs.
  2. Select the check box to the left of On Console.
    These logs are not captured anywhere and are overwritten every time you run a Job.

Error logging in a file

This section explains how to capture the logs in files.

Capturing the logs in files is a better option, because you can use the log to see details about the stats, logs and even meter/data flow. If project level logging is enabled, you do not need to separately configure components such as tLogCatcher, tFlowMeter and tStatCatcher.

Select the check box to the left of On File.

Although the screen shows static file names, they can be modified by appending a timestamp to their name. This way, you have a different log file for each timestamp. Otherwise, it would append the same file for every execution.

Error logging in a database

This section explains how to configure your project to capture the logs in a database.
  1. Select the check box to the left of On Database.
  2. Configure the database.
    For example, use a built-in MySQL database with the following tables:
    • stats_table to capture the statistics
    • log_table to capture the logs
    • meter_table to capture the data processing details