We just configure our logback.xml to have two Appenders, an AsyncAppender -> 
KafkaAppender, and FileAppender (or ConsoleAppender as appropriate).

AsyncAppender removes more failure cases too, e.g. a health check hanging 
rather than returning rapidly could block you application.

On Feb 22, 2015, at 11:26 PM, anthony musyoki <anthony.musy...@gmail.com> wrote:

> Theres also another one here.
> 
> https://github.com/danielwegener/logback-kafka-appender.
> 
> It has a fallback appender which might address the issue of Kafka being
> un-available.
> 
> 
> On Mon, Feb 23, 2015 at 9:45 AM, Steven Schlansker <
> sschlans...@opentable.com> wrote:
> 
>> Here’s my attempt at a Logback version, should be fairly easily ported:
>> 
>> https://github.com/opentable/otj-logging/blob/master/kafka/src/main/java/com/opentable/logging/KafkaAppender.java
>> 
>> On Feb 22, 2015, at 1:36 PM, Scott Chapman <sc...@woofplanet.com> wrote:
>> 
>>> I am just starting to use it and could use a little guidance. I was able
>> to
>>> get it working with 0.8.2 but am not clear on best practices for using
>> it.
>>> 
>>> Anyway willing to help me out a bit? Got a few questions, like how to
>>> protect applications from when kafka is down or unreachable.
>>> 
>>> It seems like a great idea for being able to get logs from existing
>>> applications to be collected by kafka.
>>> 
>>> Thanks in advance!
>> 
>> 

Reply via email to