[
https://issues.apache.org/jira/browse/LOG4J2-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798821#comment-16798821
]
geeta commented on LOG4J2-2569:
-------------------------------
# If all loggers are using same SQSAppender. So multiple threads are publishing
logs events to same SQSAppender. If the rate of log generation is high, how
does SQSAppender expected to handle. I assume will have to create a buffer to
keep all those log events but is this buffer management appender needs to take
care or log4j already provides - if not using AsyncLogger but using
asyncAppender.
# Is SQSAppender single instance responsible for appending all the logs ? If
yes, then this appender will have to create multiple threads, to ensure
parallel processing of the log events, and in turn keeping multiple connections
to AWS SQS.
> 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)
