| commit | 3ccc06f89a1c63397b81c98951828874e2388f98 | [log] [tgz] |
|---|---|---|
| author | Sunil Unnava <su622b@att.com> | Thu Feb 22 16:48:55 2018 -0500 |
| committer | Sunil Unnava <su622b@att.com> | Thu Feb 22 16:49:20 2018 -0500 |
| tree | 1a85ab4e875e67287d0d61fe6965ced5fea9ef45 | |
| parent | 952b238717fbc558d7b017c531220f246921d968 [diff] |
Security Fixes Issue-ID: DMAAP-206 Change-Id: Iac2cfe2c41df6d05e765e21b4f5297a032f447cd Signed-off-by: Sunil Unnava <su622b@att.com>
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