I have some complex jobs deployed and they usually runs with "Info" or "Warn" log level set.
Sometimes I would have SQL Query logged but when I set Log4J level to Debug I get hundreds of thousands log rows like:
[DEBUG]: part_kpi.part_technical_kpi_calculation_2_9.PART_Technical_KPI_Calculation - tPostgresqlInput_1 - Retrieving the record 2.
that makes huge logfiles.
Any chance to have those kind of rows switched-off?
Thank you in advance,
You can if you can change the log4j.xml file that is provided with the job. I haven't tried thiough. You can be very selective if you understand log4j configuration well.
You can try using twarn component if you place b/w 2 components you can get the row value into the logger message like row1.columnname ,
i think you can write a logger message using itinerary operator like row1.columnname == conditionvalue ? row1.columnname : ""
The first 100 community members completing the Open Studio survey win a $10 gift voucher.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Find out how Forrester rate different iPaaS and Hybrid Integration Platforms
Create systems and workflow to manage clean data ingestion and data transformation.
Introduction to Talend Open Studio for Data Integration.