commit | 5519f8372acf8d4f573739b8e819f7a1e569a019 | [log] [tgz] |
---|---|---|
author | su622b <sunil.unnava@att.com> | Wed Apr 11 19:56:37 2018 -0400 |
committer | su622b <sunil.unnava@att.com> | Wed Apr 11 19:56:55 2018 -0400 |
tree | 46f968c8f84b09fa7a285444baa79d2b4d6c3deb | |
parent | c0aeea3d201d320c83cd30497ac3c3e875e3c107 [diff] |
support for post requests with auth Issue-ID: DMAAP-404 Change-Id: Iaa85ab5410472fca4dd6118d2a53efc1737609d5 Signed-off-by: su622b <sunil.unnava@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