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

Announcements
Discover how organizations are unlocking new revenue streams: Watch here
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

tRunJob not logging correct context name via tLogCatcher

Hi,

 

I know that when you use a tRunJob you can tick the Transmit whole context check box to transmit the context variables selected in the parent job. However, if you use a tLogCatcher in that subjob then it prints out the value selected on the component dropdown. This can be confusing when looking at logs as it leads you to believe a subjob is using the incorrect context variables. Is there any way to overwrite this?

Labels (2)
2 Replies
fdenis
Master
Master

the best way is to not use log catcher on subjobs and jobs.
use TAC (Talend Administration Center) to schedule your jobs and to manage faillure.
configure logs in a global db then parse it to warn about error that is the best way
Anonymous
Not applicable
Author

I don't think this is the best solution for us. If we did that we would need to give the test team access to the ESB and Jobservers to view the debug data in the logs which would also contain Talend info which is of no use to them. The current method we are using is to send the info from tLogCatcher to a dedicated log file in a shared network directory per application.