[
https://issues.apache.org/jira/browse/LOG4J2-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799079#comment-16799079
]
Ralph Goers commented on LOG4J2-2569:
-------------------------------------
Most Appenders handle asynchronous buffering just by placing the AsynchAppender
in front of them in the configuration or by using Asynchronous loggers. Only a
small few have asynchronous behavior built in. For example, the Flume Appender
has 3 variations, 2 of which use asynchronous buffering and one of those is
because Flume itself provides the capability.
If you think that an SQSAppender will require multiple threads to handle the
expected volume then perhaps SQS isn't the best choice for use as an Appender.
Some of your questions make it sound like you haven't used Log4j much. You can
configure as many Loggers and Appenders and mix and match them any way you
want. If you want multiple instances of the same Appender you can certainly do
that.
> Support for AWS SQS appender
> ----------------------------
>
> Key: LOG4J2-2569
> URL: https://issues.apache.org/jira/browse/LOG4J2-2569
> Project: Log4j 2
> Issue Type: Question
> Components: Appenders
> Reporter: geeta
> Priority: Trivial
>
> Hi,
> Current appenders supported:
> [https://logging.apache.org/log4j/2.0/manual/appenders.html]
> I want to create an appender that supports publishing events to AWS SQS. I
> dont see this appender supported by AWS SQS.
> I see log4j2 provides async loggers and async appenders as well. I am writing
> this appender and want to extend the async appender, to ensure calling thread
> is not blocked on the remote calls made.
> This appender will also take care of failure handling, of publishing to SQS
> fails.
> Is there a guideline on how to write such an appender, that is what all
> custom handling this appender will have to take care.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
