commit | c08d6b0f0a01d26e65f42213ab9c1c4dd5b86805 | [log] [tgz] |
---|---|---|
author | Varun Gudisena <vg411h@att.com> | Mon Sep 25 16:59:02 2017 -0500 |
committer | Varun Gudisena <vg411h@att.com> | Mon Sep 25 16:59:15 2017 -0500 |
tree | 3a4f8eebadab2483fd22a041ab9d911fecec2d3d | |
parent | 90a9a1d0d2a0f09f127f2ed8c81199830f5c5b26 [diff] |
Update sitepath Updated sitepath property to match group id issue-id: DMAAP-144 Change-Id: I747fef7325d83979bc7aa3ca3dde62abe8f51865 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