| commit | 5d7a8d1e5437c9e17723fe5954122f0dcc3f3835 | [log] [tgz] |
|---|---|---|
| author | varun gudisena <vg411h@att.com> | Tue Mar 27 03:51:48 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Tue Mar 27 03:51:48 2018 +0000 |
| tree | 4fd15432da559093f3671c1fe5075e1746853e56 | |
| parent | 46640318beeff8d3dfb09fe0527a653e4a911d1f [diff] | |
| parent | 4b673b2dfbc7d6df8f5de8b64d6e08ecac3de6da [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