How to intercept and customize logging for API call details (like response time) within Talend Data Integration (DI) jobs, specifically for components like tRestRequest and tRestResponse.
The goal is to route these specific, detailed logs directly to talend esb.log file or an ELK stack.
How To
Analysis and Conclusion
Existing Functionality: The required interception logic (logging details before/after a request) is already handled by the Service Activity Monitoring (SAM) module inside the ESB Karaf container. Documentation on SAM: introduction-to-service-activity-monitoring | Qlik Talend Help
Recommendation: Because of the existing SAM functionality, there is no need to re-implement this low-level interception logic within the design of the DI job itself.
Action Plan
It will proceed with creating own automatic log routing system that will ingest event data directly from the existing SAM event database and send it to their ELK stack.
Next Steps for Detailed Customization
For more detailed or advanced log customization regarding service request interception it should submit a formal feature request via the official platform: Feature Request Link | Qlik Ideation
The Qlik Talend Professional Services team can provide custom solutions.
