Skip to main content Skip to complementary content

Using tChronometerStart and tChronometerStop for error handling

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.


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

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!