| commit | 6796dc92c4fa0b117abb37261986381a5869a6e9 | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Thu Feb 25 15:29:23 2021 +0000 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Thu Feb 25 15:42:18 2021 +0000 |
| tree | 77985d493d3f0e0c211c1abf69c7ed5b0053721d | |
| parent | 3cd892be3c47f3f7a36a948ffd35aba9b4542264 [diff] |
[DMAAP CL] Update info.yaml Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I77442500166f37b7167008884d20169b19c5714f Issue-ID: DMAAP-1538
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