Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
Maybe you have an idea. I didn't find any solutions so far:
Is there a possibility to set up specific logging rules for each Talend component types?
For instance: Whenever a Connection Component is used, I want to see the Connection parameters entirely. For every tMap I want to see the amount of lines that have been transferred.
tRow-Components for single SQL statements don't need to appear in the log at all.
Do you know a way to create such a setup? Specific logging parameters for different Talend Component Types?
Thanks for any suggestions or ideas.
Jan
Hello,
I thnk you're in the same boots as we were a few years ago, I'd suggest to read these articles:
https://www.linkedin.com/pulse/talend-log4j-tips-tricks-balázs-gunics/ ( I have a bit more filter examples here)
https://community.talend.com/s/article/Log-j-tips-and-tricks-I8730?language=ja
It was written for log4j1 but log4j2 has more filters (REGEX for example 🙂 )
So go with DEBUG logs then filter out the lines you don't need.
On Remote Engine you have to use the properties based configuration. (In a Studio job via a JVM parameter you can specify the properties based config to log4j, and/or build a job and fine tune the config outside of studio.)
If you take a look here (https://help.talend.com/r/en-US/8.0/open-studio-user-guide/studio-configure-log4j) it shows you how to work with this. By default it is set to log on WARN. You may want to set it to log on INFO.
Hello,
I thnk you're in the same boots as we were a few years ago, I'd suggest to read these articles:
https://www.linkedin.com/pulse/talend-log4j-tips-tricks-balázs-gunics/ ( I have a bit more filter examples here)
https://community.talend.com/s/article/Log-j-tips-and-tricks-I8730?language=ja
It was written for log4j1 but log4j2 has more filters (REGEX for example 🙂 )
So go with DEBUG logs then filter out the lines you don't need.
On Remote Engine you have to use the properties based configuration. (In a Studio job via a JVM parameter you can specify the properties based config to log4j, and/or build a job and fine tune the config outside of studio.)
Thanks a lot for your reply. Your idea sounds like a solution I can live with.
I'll try that out 🙂