TSTATS CATCHER issue

Highlighted
Six Stars

TSTATS CATCHER issue

Hello all,

I have a scenario where we have 10 jobs in the nightly execution plan. Each job has a tstat catcher component in it which writes the logs to a control table and there is a different job which sends out the results of this control table to all the users.

 

Recently we have faced a scenario where if a particular job is failing today, the target control table is not getting updated with the failure record.

 

For Example:

Job ran Successfully on January 1st ---------> The final control table has the success record from January 1st

Job ran Successfully on January 2nd ---------> The final control table still has the success record from January 1st and not the failure record from January 2nd.

 

As a result the final email that is sent out to users is sending January 1st success info and not the January 2nd failure info.

 

Please help how to handle this scenario.

 

Thanks

Moderator

Re: TSTATS CATCHER issue

Hello,

Would you mind posting your work flow screenshots on community which will be helpful for us to address your issue?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog