| commit | 221fdaaf7db162a86b3f4450c47fa07ea217518d | [log] [tgz] |
|---|---|---|
| author | varun gudisena <vg411h@att.com> | Wed Jan 31 02:09:50 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Wed Jan 31 02:09:50 2018 +0000 |
| tree | ae85e925b50782cfd27de044f455cd0921792a7f | |
| parent | 952b238717fbc558d7b017c531220f246921d968 [diff] | |
| parent | bc50deb5322805d749adeb5e2cfa42b981d1c163 [diff] |
Merge "sonar critical for Exception handling"
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