<?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>article Qlik Talend ESB: How to intercept and customize logging for API call details within Talend Data Integration OSGI Service Jobs in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Talend-ESB-How-to-intercept-and-customize-logging-for-API/ta-p/2539192</link>
    <description>&lt;P&gt;How to intercept and customize logging for API call details (like response time) within Talend Data Integration (DI) jobs, specifically for components like &lt;STRONG&gt;tRestRequest&lt;/STRONG&gt; and &lt;STRONG&gt;tRestResponse&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;The goal is to route these specific, detailed logs directly to talend&amp;nbsp;&lt;STRONG&gt;esb.log&lt;/STRONG&gt;&amp;nbsp;file or an ELK stack.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;How To&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Analysis and Conclusion&lt;/STRONG&gt;&lt;/FONT&gt;
&lt;P&gt;&lt;STRONG&gt;Existing Functionality:&lt;/STRONG&gt; The required &lt;STRONG&gt;interception logic&lt;/STRONG&gt; (logging details before/after a request) is &lt;STRONG&gt;already handled&lt;/STRONG&gt; by the &lt;STRONG&gt;Service Activity Monitoring (SAM) module&lt;/STRONG&gt; inside the ESB Karaf container. Documentation on SAM: &lt;A href="https://help.qlik.com/talend/en-US/esb-infra-services-configuration-guide/8.0/introduction-to-service-activity-monitoring" target="_blank" rel="noopener"&gt;introduction-to-service-activity-monitoring | Qlik Talend Help&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Recommendation:&lt;/STRONG&gt; Because of the existing SAM functionality, there is &lt;STRONG&gt;no need to re-implement&lt;/STRONG&gt; this low-level interception logic within the design of the DI job itself.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Action Plan&lt;/STRONG&gt;&lt;/FONT&gt;
&lt;P&gt;It will proceed with creating own&amp;nbsp;&lt;STRONG&gt;automatic log routing system&lt;/STRONG&gt; that will ingest event data directly from the existing &lt;STRONG&gt;SAM event database&lt;/STRONG&gt; and send it to their &lt;STRONG&gt;ELK stack&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Next Steps for Detailed Customization&lt;/STRONG&gt;&lt;/FONT&gt;
&lt;P&gt;For &lt;STRONG&gt;more detailed or advanced log customization&lt;/STRONG&gt; regarding service request interception it should submit a formal feature request via the official platform:&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Ideation/ct-p/qlik-product-insight" target="_blank" rel="noopener"&gt;Feature Request Link | Qlik Ideation&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The Qlik Talend Professional Services team can provide custom solutions.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Talend ESB" id="qlik_TalendESB"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Dec 2025 07:14:44 GMT</pubDate>
    <dc:creator>wei_guo</dc:creator>
    <dc:date>2025-12-15T07:14:44Z</dc:date>
    <item>
      <title>Qlik Talend ESB: How to intercept and customize logging for API call details within Talend Data Integration OSGI Service Jobs</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Talend-ESB-How-to-intercept-and-customize-logging-for-API/ta-p/2539192</link>
      <description>&lt;P&gt;How to intercept and customize logging for API call details (like response time) within Talend Data Integration (DI) jobs, specifically for components like &lt;STRONG&gt;tRestRequest&lt;/STRONG&gt; and &lt;STRONG&gt;tRestResponse&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;The goal is to route these specific, detailed logs directly to talend&amp;nbsp;&lt;STRONG&gt;esb.log&lt;/STRONG&gt;&amp;nbsp;file or an ELK stack.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;How To&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Analysis and Conclusion&lt;/STRONG&gt;&lt;/FONT&gt;
&lt;P&gt;&lt;STRONG&gt;Existing Functionality:&lt;/STRONG&gt; The required &lt;STRONG&gt;interception logic&lt;/STRONG&gt; (logging details before/after a request) is &lt;STRONG&gt;already handled&lt;/STRONG&gt; by the &lt;STRONG&gt;Service Activity Monitoring (SAM) module&lt;/STRONG&gt; inside the ESB Karaf container. Documentation on SAM: &lt;A href="https://help.qlik.com/talend/en-US/esb-infra-services-configuration-guide/8.0/introduction-to-service-activity-monitoring" target="_blank" rel="noopener"&gt;introduction-to-service-activity-monitoring | Qlik Talend Help&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Recommendation:&lt;/STRONG&gt; Because of the existing SAM functionality, there is &lt;STRONG&gt;no need to re-implement&lt;/STRONG&gt; this low-level interception logic within the design of the DI job itself.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Action Plan&lt;/STRONG&gt;&lt;/FONT&gt;
&lt;P&gt;It will proceed with creating own&amp;nbsp;&lt;STRONG&gt;automatic log routing system&lt;/STRONG&gt; that will ingest event data directly from the existing &lt;STRONG&gt;SAM event database&lt;/STRONG&gt; and send it to their &lt;STRONG&gt;ELK stack&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Next Steps for Detailed Customization&lt;/STRONG&gt;&lt;/FONT&gt;
&lt;P&gt;For &lt;STRONG&gt;more detailed or advanced log customization&lt;/STRONG&gt; regarding service request interception it should submit a formal feature request via the official platform:&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Ideation/ct-p/qlik-product-insight" target="_blank" rel="noopener"&gt;Feature Request Link | Qlik Ideation&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The Qlik Talend Professional Services team can provide custom solutions.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Talend ESB" id="qlik_TalendESB"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 07:14:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Talend-ESB-How-to-intercept-and-customize-logging-for-API/ta-p/2539192</guid>
      <dc:creator>wei_guo</dc:creator>
      <dc:date>2025-12-15T07:14:44Z</dc:date>
    </item>
  </channel>
</rss>

