Logs & Errors Components of Talend



Logs & Errors Components

Logs & Errors Components family allow you to log information about the execution of Talend Job.

Below are the components of Logs and Errors

tLogRow

The tLogRow component is part of the Logs & Errors family of components.

tLogRow allows you to write data, that is flowing through your Job (rows), to the console.

This is useful component to aid debugging. You can simply drop it in to a data flow, to see a snapshot of data.

tAsset

It sends a non-blocking message to tAssertCatcher.
tAssertCatcher.
The tAssertCatcher component is part of the Logs & Errors family of components, and listens for non-blocking messages from tAssert and other die commands.
tChronometerStart
The tChronometerStart component is part of the Logs & Errors family of components and is used in conjunction with tChronometerStop.

tChronometerStop

The tChronometerStop component is part of the Logs & Errors family of components.
tChronometerStop records and displays the processing time of a SubJob. tChronometerStop may be used on its own, to record the processing time of a whole SubJob, or in conjunction with tChronometerStart to record from a specific SubJob.

tStatCatcher

The tStatCatcher components listens to components that have the tStatCatcher Statistics option set to true, and writes statistics information to the defined output. tStatCatcher also listens for the start and end of a Job's execution.

tStatCatcher

The tStatCatcher component catches statistics that are generated by a Job or individual components. Statistics are always collected for Jobs, components must have tStatCatcher Statistics enabled

tWarn

This component sends a non-blocking message to a tLogCatcher.


Comments

Post a Comment

Popular posts from this blog

Hadoop Architecture

Image
Hadoop Architecture Edge nodes are the interface between the Hadoop cluster and the outside network. For this reason, they’re sometimes referred to as  gateway  nodes. Most commonly, edge nodes are used to run client applications and cluster administration tools. They are often being used as staging areas for the data being transferred to hadoop system. Name Node is master and only store metadata of HDFS  – the directory tree of all files in the file system and tracks the files across the cluster. Data Node is responsible for actual data in HDFS.   Data Node and Name Node are in contant communication via Heartbeat. When a DataNode is down, it does not affect the availability of data or the cluster. NameNode will arrange for replication for the blocks managed by the DataNode that is not available. Secondary Name Node   periodically reads the file system changes logs and apply them into the fsimage file, thus bringing it up to date. This al...
Read more