Using tChronometerStart and tChronometerStop for error handling - Cloud - 8.0

Talend Studio User Guide

Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Design and Development
Last publication date
2024-02-29
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

Sample Job and its execution results.

Design

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