[jira] [Commented] (LOG4J2-2400) Support for log4j2 RedisAppender

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573795#comment-16573795 ] 

ASF GitHub Bot commented on LOG4J2-2400:
----------------------------------------

GitHub user kmeurer opened a pull request:

    https://github.com/apache/logging-log4j2/pull/206

    [LOG4J2-2400] Initial implementation of RedisAppender. (#1)

    This PR implements a dedicated RedisAppender in log4j2. More details can be found in the log4j2 ticket here: https://issues.apache.org/jira/projects/LOG4J2/issues/LOG4J2-2400?filter=allopenissues

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kmeurer/logging-log4j2 master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/logging-log4j2/pull/206.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #206
    
----
commit 93580513440963de03fb7322656ea129996fbd9c
Author: Kevin Meurer <ke...@...>
Date:   2018-08-08T20:03:07Z

    [LOG4J2-2400] Initial implementation of RedisAppender. (#1)
    
    * Initial implementation of Redis appender.
    
    * Add unit test support for Redis Appender.
    
    * Clean up implementation.
    
    * Add site documentation and clean up imports.

commit cc409e205bcb612c6f5efe0ee81e91450006176e
Author: kmeurer <km...@...>
Date:   2018-08-08T20:06:01Z

    Merge branch 'master' of https://github.com/kmeurer/logging-log4j2

----


> Support for log4j2 RedisAppender
> --------------------------------
>
>                 Key: LOG4J2-2400
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2400
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Appenders
>            Reporter: Kevin Andrew Meurer
>            Priority: Major
>
> Redis functions well as a temporary queue for event data en route to another data store. For example, Redis may be used to improve the fault-tolerance of a logging pipeline by serving as an intermediary as log events move to a separate storage layer (i.e. log4j2 - > Redis < - Logstash -> Elasticsearch).
> As a result, event processing applications may wish to use Redis instead of Kafka as a message broker. We should add support for a RedisAppender to support this use case.
> Relevant dev list thread: [https://lists.apache.org/thread.html/4967cf3cd4db367ba563143ccd1438b7c53830671881eb692642b8d9@%3Cdev.logging.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)