Logging Configuration Reference

Log4j Configuration
Field Required? Editable? Accepts SVars? Description
Logger Name Y Y N The name of the Logger. Logger name must consist of alphabet, numeric and characters (period [.], underscore [_], hyphen [-]). The name must start with a letter of the alphabet.
Appender with Level Y Y N

The destination to which log events are appended.

All events of a level equal to or lower than the specified level are logged. For the Info level, Info, Warn, Error and Fatal events are logged.

  • TRACE: All events.
  • DEBUG: Fine-grained informational events used for debugging an application.
  • INFO: Coarse-grained informational messages that highlight the progress of the application.
  • WARN: Potentially harmful events.
  • ERROR: Errors that allow the application to continue running.
  • FATAL: Errors that cause the application to fail.
  • OFF: Blocks passing messages to a parent.
Console Y Y N Select the check box in the Console column to enable console appender for the logger.
Logging Appender Reference
Field Description
Name Name of the logging appender. Appender name must consist of characters, numeric (such as period [.], underscore [_], and hyphen [-]). The name must start with characters.
Location

The fully qualified path to the log file.

Default: {0}, represents the path of the default location.
Max Size(KB)

The maximum size of each log file, in kilobytes.

Default: 10240
Max Backup Num

The number of log files to keep.

When a log file reaches the maximum size, a new log file is created. After the number of files matches the number specified, the oldest file is deleted when a new file is created. Each file is appended with a number.

Default: 25
Pattern Layout

Controls the format of the log entries for a clear text file appender. Conforms to the log4j pattern layout.

Default:

"%d{dd MMM yyyy HH:mm:ss,SSS} [%t]
[%-5p] %c %X{_cl.correlationId} - %m%n"

This string prints the date, the name of the thread that generated the event, the level of the logged event, the category of the logged event, a correlation ID (an enrichment field), a message, and a line separator. For example: 

17 Dec 2009 16:43:41,250
[Job_Executor2] [INFO ]
com.tibco.amf.hpa.tibcohost.node.TibcoHo
stNode. - Successfully finished
processing of RDA
rda6705267566599374829.zip

In addition to the default format, ActiveMatrix Service Grid - Container Edition also supports the pattern layouts extended with enrichment fields. 

%R{_cl.physicalCompId.matrix.host}
%d'{dd MMM yyyy HH:mm:ss,SSS}' [%t]
[%-5p] %c - %m%n

Note: Pattern Layout is not validated in Application Configurator. Ensure that pattern layout conforms to Log4j pattern layout.