| commit | e124aeeb689db8959f6dbee88402624ff5ea3f20 | [log] [tgz] |
|---|---|---|
| author | Ram Koya <rk541m@att.com> | Mon Oct 08 12:51:21 2018 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Mon Oct 08 12:51:21 2018 +0000 |
| tree | c9bfbb42bd5fb1fde98e27e853393d71419ad562 | |
| parent | 79f657619d0af685d68fb6515ec9f59c308bf255 [diff] | |
| parent | b74f67b60a1ba38399a79246cb42a3f99d13badb [diff] |
Merge "test file added for DmaapClientUtil.java"
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