System log configuration

You configure the system log using the log4j.properties file, located by default in the conf directory under your Marketing Platform installation. Changes to this file go into effect within 30 seconds after the file is saved.

Configuration you perform on the system log does not affect security audit reports.

Default system log settings

By default, the system log is configured as follows:

  • Log file name: platform.log

  • Log directory: Unica/Platform/logs

  • Log level: WARN

  • Number of backups: 1

  • Maximum size of log files: 10MB

Note the following.

  • If you increase the number of backups or size of the log files, verify that the machine on which the logs are stored has sufficient memory.

  • Setting the logging level higher than the default might affect performance.

Logging levels in the system log

The possible logging levels in the system log are as follows, in ascending order.

  • ERROR

  • WARN

  • INFO

  • DEBUG

  • TRACE

The higher levels include the information contained in all of the lower levels. For example, setting the level to DEBUG enables the DEBUG, INFO, WARN and ERROR traces.

If the logging level is set to DEBUG, the response messages include any SQL queries performed against the Marketing Platform data store.

Logging level settings for the whole Marketing Platform system

You can change the logging level for all components of Marketing Platform by uncommenting the desired line in the Examples section of the file. To uncomment a line, remove the # character at the beginning of the line. If you make this change, be sure to add the # symbol to the beginning of the line specifying the previous logging level.

Setting logging levels for Marketing Platform components

You can set the logging level in the system log for specific components of the Marketing Platform. These components include:

  • Localization

  • User and group processing

  • Data migration

  • LDAP integration

  • Authentication (server-side processing)

  • The Configuration pages

  • Database access

  • Various third-party libraries (for example, ibatis)

By default, the component-level logging is turned off. To debug a specific module, remove the # character at the start of each line of the module in the log4j.properties file.

Where to find more information about log4j

You can find additional information about log4j in the following ways.

  • See comments in the log4j.properties file.

  • See http://logging.apache.org/log4j/docs/documentation.html.