Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
why have you not setup timestamp showing aside "INFO" (or DEBUG...) in the log rows?
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - Command to execute: '[Ljava.lang.String;@2641e737'.
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - The command has been executed successfully.
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tPostgresqlRow_3 - Execute the query: 'delete from sla_mbg_logs_raw where date_trunc('day',event_ts) = '2017-11-13'' has finished.
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - Setting the parameters.
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - Executing the command.
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - Command to execute: '[Ljava.lang.String;@2fd66ad3'.
[INFO ]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - The command has been executed successfully.
something like
[INFO 2017-10-10 11:00:25.345]: part_kpi.part_sla_load_mbg_logs_0_2.PART_SLA_Load_MBG_Logs - tSystem_2 - Executing the command.
would be highly highly appreciated.
Regards,
Lorenzo
In the log4j settings (file -> project properties -> log4j) try to use this for the ConversionPattern:
"%d{yyyy-MM-dd HH:mm:ss} [%-5p] (%t): %c - %m%n"
This produces messages like this:
2018-03-01 14:19:45 [INFO ] (main): project.postgres_backup_main_0_1.Postgres_Backup_Main - TalendJob: 'Postgres_Backup_Main' - Start.
Hello,
You can check out "Exec time" option in Advanced settings of Run view which shows the time of running your current job.
Is it what you are looking for? Or the timestamp for the Events In Monitoring/Logging of the TAC?
Best regards
Sabrina
I'm looking for a timestamp in the TAC log rows.
Regards,
Lorenzo
In the log4j settings (file -> project properties -> log4j) try to use this for the ConversionPattern:
"%d{yyyy-MM-dd HH:mm:ss} [%-5p] (%t): %c - %m%n"
This produces messages like this:
2018-03-01 14:19:45 [INFO ] (main): project.postgres_backup_main_0_1.Postgres_Backup_Main - TalendJob: 'Postgres_Backup_Main' - Start.
hi @Dezzsoke,
Thanks for your answer, it is working fine, but i want that timestamp in UTC format,
any help??
Thanks,
Abhi529
@Gunics Balazs , we have made the changes in the log4J settings under Project settings. After that still the log is giving the same result. No timestamp is being shown for either [INFO ],[TRACE],[DEBUG]. Did this change worked?
[INFO ]: j_s_dim_osmos_ror_rv_0_1.J_S_DIM_OSMOS_ROR_RV - Jt_loadConnectionParameters_1_tFileInputDelimited_1 - Retrieving records from the datasource.
[INFO ]: j_s_dim_osmos_ror_rv_0_1.J_S_DIM_OSMOS_ROR_RV - Jt_loadConnectionParameters_1_tFileInputDelimited_1 - Retrieved records count: 6.
[INFO ]: j_s_dim_osmos_ror_rv_0_1.J_S_DIM_OSMOS_ROR_RV - Jt_loadConnectionParameters_1_tContextLoad_1 - Loaded contexts count: 6.
@Dezzsoke (Customer) , we have made the changes in the log4J settings under Project settings. After that still the log is giving the same result. No timestamp is being shown for either [INFO ],[TRACE],[DEBUG]. Did this change worked?
[INFO ]: j_s_dim_osmos_ror_rv_0_1.J_S_DIM_OSMOS_ROR_RV - Jt_loadConnectionParameters_1_tFileInputDelimited_1 - Retrieving records from the datasource.
[INFO ]: j_s_dim_osmos_ror_rv_0_1.J_S_DIM_OSMOS_ROR_RV - Jt_loadConnectionParameters_1_tFileInputDelimited_1 - Retrieved records count: 6.
[INFO ]: j_s_dim_osmos_ror_rv_0_1.J_S_DIM_OSMOS_ROR_RV - Jt_loadConnectionParameters_1_tContextLoad_1 - Loaded contexts count: 6
Superb Neat Solution!!!