Logging Appender Reference
You can create a file appender. For each appender, you specify properties.
File Appender
<LogAppender xsi:type="amxdata:FileLogAppender" attributeList />
Property | Required? | Editable? | Accepts SVars? | Description |
---|---|---|---|---|
File Path | Y | Y | Y | The fully-qualified path to the log file. The filename component of the path is appended with a number as described in 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.TibcoHostNode. In addition to the default format, TIBCO ActiveMatrix 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 When the CBE file appender is chosen, the appender's layout is set to BEF2CBELayout, whose pattern is not configurable. |
|||
Max File Size | Y | Y | Y | The maximum size of each log file in kilobytes. |
Max Backup Index | Y | Y | Y | 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: The Max Backup Index field is pre-populated with the following value: %%node_log_max_backup_index(,,,25)%% That is, to specify the Max Backup Index value, you can define a substitution variable at the enterprise level or a node level: %%node_log_max_backup_index%% If a substitution variable is not defined, the default for Max Backup Index is 25. Note:
|