9. Logging

9.1. Introduction

This section describes the customizable logging of portal messages. Logging is useful for administrators and developers mainly for qualitity ensurance of installation, configuration and portlet development. Logging is done with apaches log4j. For details see http://logging.apache.org/log4j/docs/index.html.

9.2. Customizing logging

For customization of log levels during runtime of the Portal.Node server, administrators can create/modify the file ${com.gentics.portalnode.confpath}/nodelog.properties . Changes will be recognized automatically and the logging reconfigured accordingly. By default, only FATAL and ERROR logs are written. For performance reasons it is discouraged to use log levels other than FATAL and ERROR in production systems.

Table 3.58. Standardized LogLevels

NameDescription
FATAL log very severe error events that will presumably lead the application to abort.
ERROR log error events that might still allow the application to continue running.
WARN log potentially harmful situations.
INFO log informational messages that highlight the progress of the application at coarse-grained level.
DEBUG log fine-grained informational events that are most useful to debug an application.