Using tChronometerStart and tChronometerStop for error handling - 7.3

Talend Open Studio User Guide

Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Studio
Design and Development
Last publication date
Available in...

Open Studio for Big Data

Open Studio for Data Integration

Open Studio for ESB

This section explains how to measure the time a Job or subJob takes using tChronometerStart and tChronometerStop.

Use case

An exclusive chocolate company's world marketing head wants to see a specific report every morning. The devops team decides to look at the time the Job takes to complete, to ensure that they keep an eye on the Job and never miss the service-level agreement (SLA).

Sample Job


In this example, before the file is read, the start time is captured by tChronometerStart. Towards the end, tChronometerStop captures the end time of the Job.

Apart from the use case given, these components can be used to:
  • Perform periodical audits to see the performance of each Job
  • Determine dependency wait in case there are too many source/input file streams