Log configuration

Node logs

The default configuration of a node is to log all its activity in the node.lognode-error.log, node-lifecycle.log, integration.log, integration-error.log, ui.log and audit.log files. For more information about these files, see Access log files.

You can change the log settings in two ways:

  • Edit the <installation directory>/conf/log4j.properties file – Your changes will take effect next time you start the node, and for all subsequent runs.
  • Configure logging via the Web interface – Your changes will be in effect only until you next restart the node.
  • Configure logging via JMX – Your changes will be in effect only until you next restart the node.

Edit log4j.properties file

Please refer to the official Log4j documentation to configure this file: Apache Log4J manual (external).

Use the Web interface

To access the Log configuration Web interface, by type http://<base url>/logs in the address bar of your browser.

To access this page, you must have the Access platform logs permission. For more information, see Managing rights.

This web interface enables users to modify the logging level of the various component of the node.

Use JMX

You can configure the logs via JMX with jconsole, which is bundled with the JDK.

You need to have a JDK installed on the machine, not a JRE,  as jconsole is bundled in the JDK

Connect to a node using jconsole

To find the JMX address of a node, open the log file on the server and read the first lines


2012-06-27 18:03:42,536 [FelixStartLevel] INFO platform - ###############################################################################
2012-06-27 18:03:42,539 [FelixStartLevel] INFO platform - #                                                                             #
2012-06-27 18:03:42,540 [FelixStartLevel] INFO platform - #   STARTING PLATFORM                                                         #
2012-06-27 18:03:42,540 [FelixStartLevel] INFO platform - #                                                                             #
2012-06-27 18:03:42,542 [FelixStartLevel] INFO platform - ###############################################################################
2012-06-27 18:03:42,542 [FelixStartLevel] INFO platform - Starting Gluon platform in directory '...'
2012-06-27 18:03:42,543 [FelixStartLevel] INFO platform - Platform timezone is 'Europe/Paris'
2012-06-27 18:03:42,569 [FelixStartLevel] INFO platform - Create RMI registry on port 1099
2012-06-27 18:03:42,644 [FelixStartLevel] INFO platform - Starting JMX connector at address service:jmx:rmi:///jndi/rmi://REDMOND.acme.com:1099/jmxrmi

 Find the line starting with "Starting JMX connector at address" (quote excluded) and copy the rest of the line to the clipboard.

On the node where the above logs have been written, the JMX address is service:jmx:rmi:///jndi/rmi://REDMOND.acme.com:1099/jmxrmi

Open MBean tab and select the log4j > default node

Add a logger

To change the log level of calcium.modelStorageProcessor:

  1. Click the Operations node.
  2. Enter calcium.modelStorageProcessor as a parameter for the addLoggerBean operation, then click the addLoggerBean button.

Change the level of the logger

  1. Select the log4j > calcium.modelStorageProcessor > Attributes node.
  2. Type DEBUG in the priority row (alternatively, you could type INFO, WARN or ERROR depending on the desired level).

Data integration logs

Read Data integration settings to configure the size and location of the data integration log files.


Related Links