| commit | d0fd7a9c0aca788fa5fc9109c382c57791662772 | [log] [tgz] |
|---|---|---|
| author | rn509j <rn509j@att.com> | Mon Oct 02 18:50:45 2017 -0400 |
| committer | rn509j <rn509j@att.com> | Mon Oct 02 18:53:50 2017 -0400 |
| tree | 18c816db9d39be37bfa0a4b1f8100f72de64b95f | |
| parent | 6a8bbf5d648e5c0cd95de4c89a479ae5ea5b44bc [diff] |
commiting code for test coverage DMAAP-149 Signed-off-by: rn509j <rn509j@att.com> Change-Id: Ie339f3458b08d67786b05bb7080974e2f1050044
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