I created a Job REST Service (starting with a tRESTRequest and ending with a tRESTResponse). In this Job, I used a Joblet which catchs errors, exceptions and messages and writes them into a CSV log file.
The Joblet works fine in several Jobs (the CSV log file contains the tWarn, tDie or Exceptions messages) but seems not working in my Job REST service (the log file is empty).
Is it a specific configuration for the Job Service to use tLogCatcher ?
It should work.
Maybe a miss configuration on the tFileOutputDelimited component?
If filename is based on a global var, are you sure this variable is well defined?
Hi Lilian,
nice to hear from you event if it's for a problem resolution!
It's Frederic, we met at Atlantic.
As
@manodwhb asked, can share these elements?
I hope you're fine and it's a pleasure to have some news even by Talend Community !!
I attached the Job Service design and also the Joblet design.
Don't pay attention to tLogRow before the tWarn. I added these tLogRow components to try to have log information on the Cloud task. But the log in the Cloud task as the CSV log file stay invariably empty !!
I attached also an example of the CSV log file generated by the Job Service.
It should work.
Maybe a miss configuration on the tFileOutputDelimited component?
If filename is based on a global var, are you sure this variable is well defined?
Thanks for your help. The global var which contains the absolute pathname of the CSV log file, is set after the tRESTRequest component with a global var LOGDIR set in the tPrejob part. I believed that the global vars defined in the tPrejob kept their value as long as the Job service run, But It seems that's not the case. So, I set the global var LOGDIR after the tRESTRequest and now the CSV log file contains the log messages.
