| commit | 3815da092efa0a1047b276fba2ce01ad3cb2a0ab | [log] [tgz] |
|---|---|---|
| author | su622b <su622b@att.com> | Fri Jun 28 00:25:50 2019 -0400 |
| committer | su622b <su622b@att.com> | Fri Jun 28 00:26:00 2019 -0400 |
| tree | 2f0419586a8e0f4982adfa7a2ca1e84851e0766b | |
| parent | 437cec5434271167a15c4fcdd19ab60d84774c13 [diff] |
update oparent Issue-ID: DMAAP-1125 Change-Id: Id040c4d21e354617a462cc97220696042dc003db Signed-off-by: su622b <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