| commit | b017c94fe3c1fe37471ac0c6dca22b48d37647bc | [log] [tgz] |
|---|---|---|
| author | varun gudisena <vg411h@att.com> | Mon Mar 26 21:45:55 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Mon Mar 26 21:45:55 2018 +0000 |
| tree | 1d5a5983a4275140964e6c45c2b4789fbae95070 | |
| parent | 8c97df99eb091e188e1263cadc7f8a2007cb1612 [diff] | |
| parent | e97eaab01db540d1462bd7464dcad355faed437a [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