| commit | 7224f4b74c1e17482434957756c56d72b56d15bf | [log] [tgz] |
|---|---|---|
| author | sunil unnava <su622b@att.com> | Tue May 14 16:35:14 2019 +0000 |
| committer | Gerrit Code Review <gerrit@onap.org> | Tue May 14 16:35:14 2019 +0000 |
| tree | 2fd52c4e9c7147e5f07ca9e6c92a83030e9b55fe | |
| parent | dcb1479b85dc4fa43d7e417a05d01ac153b7fd1f [diff] | |
| parent | b4b90fb98210c090357d024aac2518bf50b284de [diff] |
Merge "adding Fiachra Corcoran to INFO.yaml as a committer Issue-ID: DMAAP-1189 Change-Id: I76c5c02f60cde2a091c7bb62c019243b8f4ffbd9 Signed-off-by: sawantmandar <ms5838@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