How to know where logs are output from

[panda1]

There are often some warnings and errors in the log. It seems that it is not output by me in the script, but the system log, but the log shows that it was created by me

Is there a way to know where a log is output from?

If there is no way, someone knows what is the reason for such a log, I want to check

1.Such logs often appear in my log, but I don't remember writing such scripts,what is xml_baseline_string,What's the reason for this

source:Evaluator
org.mozilla.javascript.EcmaError: "xml_baseline_string" is not defined.
Caused by error in  at line 1

==> 1: xml_baseline_string

2.String index out of range,This looks like a Java exception,This error often occurs, but I don't know why. Only one error appears in each log.What caused this log to appear

source:com.glide.ui.ServletErrorListener
String index out of range: 0: java.lang.StringIndexOutOfBoundsException: String index out of range: 0: java.lang.String.charAt(String.java:658)
com.glide.sys.LoggingExclusionChecker.findTableNameForEmbeddedHelpURI(LoggingExclusionChecker.java:272)
com.glide.sys.LoggingExclusionChecker.shouldRedactDataInLogs(LoggingExclusionChecker.java:153)
com.glide.processors.Processor.logParameters(Processor.java:144)
com.glide.processors.AProcessor.runProcessor(AProcessor.java:568)
com.glide.processors.AProcessor.processTransaction(AProcessor.java:266)
com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:181)
com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:169)
com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:44)
com.glide.sys.Transaction.run(Transaction.java:2406)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

I look forward to your reply. Thank you very much

[Nayan Mahato · Accepted solution]

Hi Panda,

This is a platform-wide known error log In Rome EA release or Quebec Patch 8 not specific to any of your scripts. So please ignore it.

There is a problem ticket open in ServiceNow. PRB1513630

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0996113

Regards,

Nayan