| commit | d67984ed3c9018b45aa1227bf93ccf7ebca7cd3e | [log] [tgz] |
|---|---|---|
| author | Jessica Wagantall <jwagantall@linuxfoundation.org> | Mon Jan 14 17:52:27 2019 -0800 |
| committer | Jessica Wagantall <jwagantall@linuxfoundation.org> | Mon Jan 14 17:52:27 2019 -0800 |
| tree | 55f2969a96a049a6be2e3643413822fdbafddef6 | |
| parent | ca98537bd0271d4d3450a0bf7723bcdd5ce9d249 [diff] |
Update INFO.yaml file Change-Id: I8819b0a81c12d8c19600672de4c240e6e2d0b4a5 Issue-ID: CIMAN-134 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
To configure a MR Log4J appender the following parameters are available:
(R) Topic [String] - The topic which you wish to publish your log messages to (R) Partition [String]- The partition within the Topic that you wish you publish your log messages to (R) Hosts [String]- A comma separated string containing the MR API server nodes you wish to connect to (O) MaxBatchSize [Integer] - The maximum size of the batch of log messages. When the batch grows larger than this, the messages are flushed to the topic/partition. (O) MaxAgeMs [Integer] - The maximum age in milliseconds of the batch. When the batch age is older than this, the messages are flushed to the topic/partition. (O) Compress [Boolean] - Indicates whether you would like your messages compressed or not.
An example can be found in ./src/main/resources/log4j.xml