| commit | e8260cf23ae90b3afad9ac5e5e5777843fc7a261 | [log] [tgz] |
|---|---|---|
| author | varun gudisena <vg411h@att.com> | Mon Apr 09 23:22:21 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Mon Apr 09 23:22:21 2018 +0000 |
| tree | 14d40937069cb7e3b11e06b2dc8186a516c212fa | |
| parent | 7320c21c0eaf99979f74c85044b0082d9b496db3 [diff] | |
| parent | 9b15d3e20c77b6a88e2441d355fe4c196ec05bd7 [diff] |
Merge "Sonar critical issues"
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