| commit | 5d8ec67db97bdb61b0c07c46afb3a58a02661274 | [log] [tgz] |
|---|---|---|
| author | micdzied <michal.1.dziedzic@nokia.com> | Thu Jul 04 14:01:31 2019 +0200 |
| committer | micdzied <michal.1.dziedzic@nokia.com> | Thu Jul 04 14:01:31 2019 +0200 |
| tree | 45d79130517d85d69fc3a08a146574ac9317ee58 | |
| parent | 3815da092efa0a1047b276fba2ce01ad3cb2a0ab [diff] |
code improvement Change-Id: Idc402a05d24c89e5cafc3a4d4221ec2158876f0a Issue-ID: DMAAP-1229 Signed-off-by: micdzied <michal.1.dziedzic@nokia.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