| commit | cc9de9bc6803212f0233e0e1bf06aa63fe8b7a6a | [log] [tgz] |
|---|---|---|
| author | Varun Gudisena <vg411h@att.com> | Wed Aug 30 20:49:32 2017 -0500 |
| committer | Varun Gudisena <vg411h@att.com> | Wed Aug 30 20:50:47 2017 -0500 |
| tree | 7425883592f6cfe97c415f17ca80a0ba13041ce2 | |
| parent | ffc0ccd5ab1ad5e6a5db2d674a4a6c30a31bc732 [diff] |
Add Initial Code Import Intial Code import for dmaapClient Issue-id: DMAAP-82 Change-Id: Ib627672d37e233b796619f93dd91f5caaf1592e4 Signed-off-by: Varun Gudisena <vg411h@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