You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2019/03/22 05:47:00 UTC

[jira] [Commented] (LOG4J2-2569) Support for AWS SQS appender

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

Ralph Goers commented on LOG4J2-2569:
-------------------------------------

The best way to learn how to write an Appender is to look at existing ones that are distributed with Log4j. 

All Appenders use a Manager. When a reconfiguration occurs a new Appender will be created but the Manager from the previous configuration will be used if it matches the new one. This helps prevent losing log events during reconfiguration. As with many entities in Log4j, it is preferable for many configurable properties to be immutable. This helps prevent race conditions or multi-threading issues. The down-side of these practices means that some changes to an Appender configuration may not have any effect during a reconfiguration. 

For any component to be accepted to Log4j it must come with unit tests that test for both proper and improper configurations as well as errors that can occur during execution.as much as is reasonably possible. It should also conform to our coding guidelines.

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