topic Re: Capturing the job log in the client in Talend Studio

Capturing the job log in the client

PhilHibbs — Tue, 11 Dec 2018 09:27:39 GMT

There are plenty of threads about job logs, but they all involve amending the job to write log information. What I want is simply to capture the output that appears in the output pane when you run a job in the client. The TAC does this automatically, but I want to do it in the client.

The client appears to be limited in the number of lines that it can keep, even if "Line limit" is not checked. I have a master job that runs about 10 sub-jobs, some in loops, and the log is many thous ands of lines long. Is there a simple way to get the Talend client to write all that log to a file?

Re: Capturing the job log in the client

Anonymous — Tue, 11 Dec 2018 11:05:41 GMT

I believe this mini tutorial explains precisely what you need....

https://community.talend.com/t5/How-Tos-and-Best-Practices/Redirect-the-output-from-the-console-to-a-file/m-p/133814#M598

Re: Capturing the job log in the client

PhilHibbs — Tue, 11 Dec 2018 17:47:09 GMT

I guess that's as close as I'll get, shame it needs me to hack the job, I'll have to remember to take it out before deploying to production! Thanks.

Re: Capturing the job log in the client

Anonymous — Tue, 11 Dec 2018 22:29:24 GMT

Just wrap it in an IF condition with a context variable used to turn it on or off. If you use the Implicit Context Load functionality you can use this sort thing to switch on and off debugging code in a production environment.

Re: Capturing the job log in the client

PhilHibbs — Wed, 12 Dec 2018 08:37:03 GMT

Sure, good suggestion, I do have some "debug" context variables already. I don't even want this to happen all the time in test environment, I only want the log if the job is failing and I need it to figure out why!