Debug log entry

balaji_prusty1
Giga Guru

‎08-16-2022 07:33 AM

Hi All;

The system log keeps on creating entries for some transactions, but I cannot find the entry's source to disable. As per the context map, it is showing a scheduled job that I already disabled but still the same issue. Can anyone please help with this to find the root cause? here are the logs (Attached).

 

{"_scope":"global","_user":"system","_script_record":"87cb3a3397855d10c689737e6253afe2","_txid":"8b7cbeb7874d191028bdfee4dabb3596","_session_id":"glide.scheduler.worker.2","_script_table":"sysauto_script"}

 

find_real_file.png

Labels:
Preview file
111 KB
  • 1,589 Views
1 REPLY 1

Geoffrey Bishop
Tera Contributor

‎10-10-2022 01:51 PM

Hello @balaji_prusty1 

Did you already see this knowledge base article?:  Troubleshooting excessive logging (syslog) 

 

I am working on a similar problem.  I was hoping to create a log function which points BACK to the original script which created the log, and would tell me:  "Table X.  Sys_Id Y".

That way, any log which is generated can be traced back to its source and modified or disabled if necessary...

 

It's good that you found the Context Map field of the syslog entries.  I did not even realize that existed until today.

And adding that field to the syslog form provides good information, as you show in your screenshot.

 

Have you tried looking up the Transaction Id (_txid) value in the Transaction Log?  That provides even more information, especially in the URL field, but in my case it did not help.  I logged a message from a business rule on the Incident table, and I was hoping to find the sys_id of that business rule somewhere; either in the syslog table or the syslog_transaction table.  No luck though.  😕

0 Helpfuls