| commit | 58a6137c826c7b2127f16ed2c916d0a27cff29a8 | [log] [tgz] |
|---|---|---|
| author | david.mcweeney <david.mcweeney@est.tech> | Wed Jul 14 11:06:10 2021 +0100 |
| committer | david.mcweeney <david.mcweeney@est.tech> | Wed Jul 14 15:35:32 2021 +0100 |
| tree | cae7f1569005b0cf58a7131300a9566662a5629f | |
| parent | 34db7e236b2864fe7a0732a84522730264b6138d [diff] |
DMAAP-DC - Update Info.yaml Change-Id: I45661698cb3b1b820751f60dd07d65fbc29488bc Signed-off-by: david.mcweeney@est.tech Issue-ID: DMAAP-1635
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