Logging Appender Reference
[Delete this text and replace it with your own content. ]
[The reference topic contains the information user might refer to complete it task, such properties values. This often contains a table for reference. Apply the Tables.css tables styles to the table.]
| Field | Description |
|---|---|
| Name | Name of the logging appender. |
| 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. |
| 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 is deleted when a new file is created. Each file is appended with a number. Default: 25 That is, to specify the Max Backup value, you can define a substitution variable: %%node_log_max_backup_index%%. |
| 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
|