<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Specific log4j logging level for each Talend Component? in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344205#M111887</link>
    <description>&lt;P&gt;Thanks a lot for your reply. Your idea sounds like a solution I can live with.&lt;/P&gt;&lt;P&gt;I'll try that out &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2023 12:54:10 GMT</pubDate>
    <dc:creator>jhuebler</dc:creator>
    <dc:date>2023-01-30T12:54:10Z</dc:date>
    <item>
      <title>Specific log4j logging level for each Talend Component?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344202#M111884</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe you have an idea. I didn't find any solutions so far:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a possibility to set up specific logging rules for each Talend component types?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;tRow-Components for single SQL statements don't need to appear in the log at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know a way to create such a setup? Specific logging parameters for different Talend Component Types?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any suggestions or ideas.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jan&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2024 22:10:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344202#M111884</guid>
      <dc:creator>jhuebler</dc:creator>
      <dc:date>2024-11-15T22:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: Specific log4j logging level for each Talend Component?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344203#M111885</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 16:30:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344203#M111885</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-01-25T16:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: Specific log4j logging level for each Talend Component?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344204#M111886</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I thnk you're in the same boots as we were a few years ago, I'd suggest to read these articles:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.linkedin.com/pulse/talend-log4j-tips-tricks-bal%C3%A1zs-gunics/" alt="https://www.linkedin.com/pulse/talend-log4j-tips-tricks-bal%C3%A1zs-gunics/" target="_blank"&gt;https://www.linkedin.com/pulse/talend-log4j-tips-tricks-balázs-gunics/&lt;/A&gt; ( I have a bit more filter examples here)&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.talend.com/s/article/Log-j-tips-and-tricks-I8730?language=ja" alt="https://community.talend.com/s/article/Log-j-tips-and-tricks-I8730?language=ja" target="_blank"&gt;https://community.talend.com/s/article/Log-j-tips-and-tricks-I8730?language=ja&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It was written for log4j1 but log4j2 has more filters (REGEX for example &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So go with DEBUG logs then filter out the lines you don't need.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.)&lt;/P&gt;</description>
      <pubDate>Sun, 29 Jan 2023 15:05:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344204#M111886</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-01-29T15:05:18Z</dc:date>
    </item>
    <item>
      <title>Re: Specific log4j logging level for each Talend Component?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344205#M111887</link>
      <description>&lt;P&gt;Thanks a lot for your reply. Your idea sounds like a solution I can live with.&lt;/P&gt;&lt;P&gt;I'll try that out &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 12:54:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Specific-log4j-logging-level-for-each-Talend-Component/m-p/2344205#M111887</guid>
      <dc:creator>jhuebler</dc:creator>
      <dc:date>2023-01-30T12:54:10Z</dc:date>
    </item>
  </channel>
</rss>

