Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

How to Log everything my job does?

Hi,
I want to log everything my talend job does.
When running my job within talend I can see on the gui where the flow currently is, what its doing and it shows whether a flow was true, false, ok or error.
When deploying the executables of my job to a server and running it automated there I do not geht this information any more.
Of course I am able to do logs at several points but I dont want to create a log componenten after each single working-component, thats too much overhead.
Of course I could catch errors, but in my case the problem is, the process does not end its only reproducable on deployment not local with my open studio.
Thats why I want to catch as much information about all components and subjobs as possible.
We often get the case to have a look at any unknown behavior and it were much more comfortable to have A big log to look after.
Is there a way to get a predefined all logging-log like I am looking for?
Any suggestions else for easily creating something like this? (it mus be then a generic solution, not like creat a log componentent after every single working-component).
Thanks in advance.
Labels (2)
10 Replies
billimmer
Creator III
Creator III

For input components I use the NB_LINE variable and write it with tWarn.  The when I load data into the DB, the Talend DB component will error if the records cannot be written, such as a tDBbulkExec or tDbOutput.

 

For the "tDbRow" components, I wrap my sql to return a count.  Then I use a tParseRecordSet to get the value of "RecCnt" and write it into the log with tWarn.  For example:

 

WITH rows AS (
DELETE FROM mydatabase.myschema.mytable
WHERE "YYYYMM" >= '202004'
RETURNING 1
) SELECT count(*) AS "RecCnt" FROM rows;

 

If there is an easier way to do this I'd also like to know.  I don't think tStatCatcher writes record counts.  I wish it did.