| commit | d87c09894ad714e711ea2e10844262182d226fa3 | [log] [tgz] |
|---|---|---|
| author | rama-huawei <rama.subba.reddy.s@huawei.com> | Mon Sep 18 15:25:58 2017 +0530 |
| committer | Rama SubbaReddy <rama.subba.reddy.s@huawei.com> | Mon Sep 18 10:15:01 2017 +0000 |
| tree | ab50409147f13679150641e5cda7b4d0dab7ccd2 | |
| parent | 3ad76692b6bddfec077b4ad673694d7e97c98743 [diff] |
Fix for Sonar Major issues DCAEGEN2-93 Change-Id: Id3b2e134d4e5b8c63712071d672b6ba6e40ab6f4 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
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