Appenders in Log4J describe an end point to send the log data/ event object to.

So you can have a rolling_file ,�� socket TCP connection, MQ , DB table , console ... any you�� need, many already provided with their custom code to pipe the info to the end point.

Appenders are now configurable ( in code ) typically in XML to be able to pipe it to a file in Production / or a DB . While in dev it is to the console.

You can have the same log sent to multiple Appenders with events filtered logically for each of them, with one of the Appender getting the whole dump of events.

The critical issue in logging is performance impact of logging too much.

On Tue, Jan 13, 2015 at 5:46 PM, stepharo <stepharo@free.fr> wrote:

These are nice. There is still value in Log4s with its variery of appenders.

what is an appender?

And yes soon I will come back to Beacon+SystemLogger+