RE: status appender?

getting their events to our API. Our API will consist of several "protocol" endpoints, like HTTP, FTP, MQ, etc. These endpoints will accept events and then funnel them to an HDFS data lake. Thanks, Nick > From: remko.po...@gmail.com > Subject: Re: status appender? > Date:

Re: status appender?

It's called StatusListener: http://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/status/StatusListener.html On 14 December 2015 at 09:34, Nicholas Duane wrote: > I'm curious if there is such a thing as a StatusAppender in log4j2 which, > as you would

Re: status appender?

First, what you are wanting to do is, in fact, pretty normal. However, by default the StatusLogger that Log4j uses for its components doesn’t use an Appender. Although the API is the same the internals of the StatusLogger are actually quite different than the “normal” Log4j implementation.

RE: status appender?

uting" within the code. Our filter on the http appender already filters out anything less specific than INFO. Thanks, Nick > Subject: Re: status appender? > From: ralph.go...@dslextreme.com > Date: Mon, 14 Dec 2015 09:32:51 -0700 > To: log4j-user@logging.apache.org > > First

RE: status appender?

ere. It's about how to send INFO - ERROR to one location, or possibly two, and have DEBUG only go to the status logger. There is push back on "failing over" the events from the domain socket appender so that code might get pulled out. Thanks, Nick > Subject: Re: status appender? > Fro

Re: status appender?

thinking that one other solution would be to log all events within > our DomainSocketsAppender to both its private logger and the status logger, > thus somewhat removing the "routing" within the code. Our filter on the http > appender already filters out anything less specifi