Enable SLF4J to Log4J2 bridge for 6.x

[svrc]

This should enable Kafka logging in Log4J2 now, which was broken since the switch to Log4J2. Also README now clarifies how to set the Kafka log level in the Log4j2 properties.

[jordansissel]

Code looks good, but I haven't tested yet.

[jordansissel]

Confirmed with this code Kafka outputs more logging, however, setting the log level seems to have no effect:

logger.kafka.name=org.apache.kafka
logger.kafka.appenderRef.console.ref=console
logger.kafka.level=warn

Kafka still outputs INFO logs to console.

[svrc]

I admit I hadn't tested this to make logs less verbose (i.e. WARN), but it worked for me to make them more verbose (i.e. DEBUG). I can see if I can replicate.

[jordansissel]

@svrc-pivotal I tried debug initially, but I didn't see any extra logging (no [DEBUG] in the output), so I tried warn instead.

I am only testing startup (output starts up, does nothing else) though, not message processing.

[svrc]

Oh yes, you'd only really notice this at messaging time as the Kafka classes won't get touched. I notice that on startup everything is always locked to INFO no matter what I did... Anyway, I'll see if I can reproduce this with a script with actual message flow for you with WARN and DEBUG. Stu

…

On Mon, Oct 2, 2017 at 3:07 PM, Jordan Sissel ***@***.***> wrote: @svrc-pivotal <https://github.com/svrc-pivotal> I tried debug initially, but I didn't see any extra logging (no [DEBUG] in the output), so I tried warn instead. I am only testing startup (output starts up, does nothing else) though, not message processing. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#134 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKJcr8aXxQ0l23q67MoC6pxU7GTQQhaoks5soVCVgaJpZM4NcyhB> .

-- Stuart Charlton Pivotal Software | Platform Architecture Mobile: 403-671-9778 | Email: [email protected]