Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Lorenzo5
Creator
Creator

log timestamp missing?

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

Labels (3)
1 Solution

Accepted Solutions
Dezzsoke
Contributor III
Contributor III

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.

View solution in original post

7 Replies
Anonymous
Not applicable

Hello,

You can check out "Exec time" option in Advanced settings  of Run view which shows the time of running your current job.

0683p000009LrnG.png

Is it what you are looking for? Or the timestamp for the Events In Monitoring/Logging of the TAC?

Best regards

Sabrina

Lorenzo5
Creator
Creator
Author

I'm looking for a timestamp in the TAC log rows.

 

Regards,

Lorenzo

Dezzsoke
Contributor III
Contributor III

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.

Anonymous
Not applicable

hi @Dezzsoke,

Thanks for your answer, it is working fine, but i want that timestamp in UTC format,

any help??

Thanks,

Abhi529  

Swapnadeep
Contributor
Contributor

@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.

Swapnadeep
Contributor
Contributor

@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

seanbruton

Superb Neat Solution!!!