commit | 4dfba6f5c5804b3af25476ad0c9e9dc9474d4df6 | [log] [tgz] |
---|---|---|
author | varun gudisena <vg411h@att.com> | Mon Sep 25 16:40:57 2017 +0000 |
committer | Gerrit Code Review <gerrit@onap.org> | Mon Sep 25 16:40:57 2017 +0000 |
tree | 365a77f02f79c56e7263a8fb143e73adb2f856a1 | |
parent | 3e2d834ce52064d292f4f4928eb210682ede4437 [diff] | |
parent | 90a9a1d0d2a0f09f127f2ed8c81199830f5c5b26 [diff] |
Merge "Fix stage site jenkins jobs"
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