Upon calling "gs.logError()" API, it creates duplicate error-level syslog records!!SummaryUpon calling "gs.logError()" out of box API, it creates duplicate error-level syslog records!! Steps to Reproduce Try something like below in background scripts: var gl = new GSLog('incident');gl.logError("This is a Trail Run"); Notice similar to below type of errors in the logs: Created Level Message Source2020-10-14 09:31:47 Error This is an error message *** Script 2020-10-14 09:31:47 Error *** Script: This is an error message: no thrown error com.glide.ui.ServletErrorListener Related LinksComments from development team: 1. Why the error shows : no thrown error 2020-10-14 09:31:47 Error * Script: This is an error message: no thrown error com.glide.ui.ServletErrorListener After checking code, it was expecting an actual Java Exception or Throwable (via a string name). So if you pass it something like thisgs.logError("This is a test","ArithmeticException");You will get something more expected in the Error logArithmeticException: This is a test: no thrown error`. This should also accept any name of a Java Exception. 2. When 'gs.logError()' is called there's always a side effect of writing a source==com.glide.ui.ServletErrorListener error-level syslog record that duplicates the requested message. In the server, the exception (Throwable <exception> t) is used to provide stack trace information to the logger in the backend/server. If there is no exception that was thrown (passed as a parameter ["Throwable t"] to the logging methods [error, warn]), then the logger will print "no thrown error", because there was no exception thrown/passed. If an exception was thrown (passed as a parameter), then a stack trace (generated/extracted from the exception) would be appended to '<message> + <exception class name>', and that would be printed instead of the <message> + ': no thrown error.'What's happening is that the primary error message is logged, then the error message is logged again with the stack trace if an exception was thrown. When there is no exception, the log looks almost like a duplicate log entry because there is no stack trace to include. So, I believe the customer should always expect this behavior when using gs.logError(). 3. Why this doesn't occur with a warning?Are the implementations for warning and error different? The implementation for Warning and Error are only slightly different (mostly the same), but the main difference is that the server has the ServletErrorListener which picks up ANY broadcast error message for the logging system and also prints it as described.Since the duplicate errors are coming based on the current design and not a blockage for the customer, this can not be considered as bug.