[
https://issues.apache.org/jira/browse/LOG4J2-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638739#comment-17638739
]
Volkan Yazici commented on LOG4J2-2400:
---------------------------------------
{{RedisAppender}} has been in the making in {{master}} for several years
without much interest from the community. Next to that there are [battle-tested
feature-rich community
alternatives|https://github.com/vy/log4j2-redis-appender] available. Removing
{{RedisAppender}} from {{master}}.
> 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
> Fix For: 3.0.0
>
>
> 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
(v8.20.10#820010)
