| commit | cd2ea8442c6991a360cb349433ca38e753fbdd4e | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Mon Oct 10 13:40:26 2022 +0100 |
| committer | efiacor <fiachra.corcoran@est.tech> | Mon Oct 10 13:40:30 2022 +0100 |
| tree | 7f54f3790fe3ebdb0d3f820468d8304399459267 | |
| parent | 9366906e17713b97bf26c6d920d3fb69342ef657 [diff] |
[DMAAP-CLIENT] Release 1.1.13 Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I9164a137efd206dc972e347241ac5c57dd6712a6 Issue-ID: DMAAP-1748
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