RE: status appender?

Good question. We currently have an instrumentation framework, in .NET, which we use to log events and capture centrally. This was developed back in 2001 and has served us well. When we discussed capturing these new events we decided that it would be best to use a leading logging framework

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?

Thanks. Yes, that's the one option I was thinking of. Adding a console or file appender to our logger. However, the actual class in question is our DomainSocketAppender. This is somewhat related to a previous question I asked about capturing events from our appenders centrally. I guess in

RE: status appender?

I'll give a brief description on the setup so that hopefully you have a better picture. We want to capture a specific type of event, let's say a business event, from all the applications on the box and get them to a central location. We're also looking ahead to a possible PaaS environment and

Re: status appender?

I don’t think I understand - “we’re writing to our own logger within our DomainSocketAppender”. The status logger in your appender should only be logging errors or other events that occur within that Appender, which normally would be nothing. Routing events being processed by an Appender