| commit | 67cf034d0e2df6dbfb7043395671f6520972f976 | [log] [tgz] |
|---|---|---|
| author | varun gudisena <vg411h@att.com> | Thu Feb 22 21:59:11 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Thu Feb 22 21:59:11 2018 +0000 |
| tree | 1a85ab4e875e67287d0d61fe6965ced5fea9ef45 | |
| parent | 221fdaaf7db162a86b3f4450c47fa07ea217518d [diff] | |
| parent | 3ccc06f89a1c63397b81c98951828874e2388f98 [diff] |
Merge "Security Fixes"
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