You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Kevin Andrew Meurer (JIRA)" <ji...@apache.org> on 2018/08/07 16:56:00 UTC
[jira] [Updated] (LOG4J2-2400) Support for log4j2 RedisAppender

     [ https://issues.apache.org/jira/browse/LOG4J2-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Andrew Meurer updated LOG4J2-2400:
----------------------------------------
    Description: 
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]

  was:
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


> 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)