commit | 3a979a8705e54d4607f6524ea09aaa1f10fe8d27 | [log] [tgz] |
---|---|---|
author | sunil unnava <su622b@att.com> | Tue May 14 17:43:03 2019 +0000 |
committer | Gerrit Code Review <gerrit@onap.org> | Tue May 14 17:43:03 2019 +0000 |
tree | bdf920d65f73088c21f8dcdee85af940b61a9d36 | |
parent | 7224f4b74c1e17482434957756c56d72b56d15bf [diff] | |
parent | de993a59814af4a63496c03a823b3cdc41641f2e [diff] |
Merge "Fix too many constructor param in dmaapclient"
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