Adding interpreter log information to the xMatters 5.0 logs

Issue Details

The xMatters node logs (AlarmPoint.txt or AlarmPoint..txt) do not contain the interpreter log information that some clients relied on to troubleshoot script problems, such as how each line of the scripts is executed.

An example of interpreter log information:

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: # Use this script to setup default behaviours and to perform basic notifications.

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: IF (EXISTS($event.debug))

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: ENDIF

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: # The AlarmPoint URL used for the response links and HTML Logo.

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: # This should be the URL of the AlarmPoint webserver

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: $main.alarmpointURL = "http://localhost:8888/"

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: # Construct the response URL

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: # NOTE This must be modified to match the URL of the deployment.

2012-08-15 11:49:18,670 [processBroker-process-pool-thread-6] DEBUG Default Company EV[200006] -  - Interpreter Runs: @company = @event::getCompany()

......

Issue Cause

In xMatters 5.0, the interpreter log information was changed to be associated with "TRACE" level logging, and moved to a separate log file named script_runs.log, and stored in the same directory as the other node logs.

Resolution

To view the interpreter log information in AlarmPoint.txt or AlarmPoint..txt, first ensure that the node logging level is at TRACE level or higher (i.e., set to TRACE or Detailed (All).

Open the <xMHOME>\node\assets\config\log4j.xml, and remove or comment out the following lines:

<logger name="com.invoqsystems.foundation.interpreter.invoqscript.processor.ScriptTask" additivity="false">  
  <appender-ref ref="SCRIPT_RUNS"/>  
</logger>  

Save the log4j.xml file, and then restart the node.

xMatters Reference

DTN-3087, SUP-6509, JDN-4027

Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk