Re: StatusLogger Urgent

StatusLogger is part of log4j-api-2.13.0.jar. Ralph > On Feb 20, 2020, at 6:47 AM, EDMONDO SENA wrote: > > > Hi, > > In log4j2, is there an equivalent of log4j 1.x' > LogLogfor > internal logging purposes? >

Re: StatusLogger Urgent

StatusLogger is the correct one when writing plugins for Log4j2. If you’re upgrading a custom plugin from version 1, you need to change which classes it references. On Thu, Feb 20, 2020 at 07:47 EDMONDO SENA wrote: > > Hi, > > In log4j2, is there an equivalent of log4j 1.x' > LogLog< >

Re: StatusLogger Multiple logging implementations found

I think what you are trying to say is 1. Your app needs to use Log4J 1.x. 2. You are trying to include something that is using the Log4J 2 api. The problem you are encountering is that you have provided 2 implementations of the Log4J api - log4j-to-slf4j and log4j-core. You can only have one of

Re: StatusLogger

roth element of the parameters array to be the > original object that was logged? > > Thanks, > Nick > >> Subject: Re: StatusLogger >> From: ralph.go...@dslextreme.com >> Date: Fri, 20 Nov 2015 12:08:38 -0700 >> To: log4j-user@logging.apache.org >> >> OK - so it so

RE: StatusLogger

I'm not necessarily after the string. I'm trying to get the original object that was passed to one of the logging methods. It could have been a string or some complex object. Thanks, Nick > Subject: Re: StatusLogger > From: ralph.go...@dslextreme.com > Date: Mon, 30 Nov 2015 08:30

Re: StatusLogger

original object > that was passed to one of the logging methods. It could have been a string > or some complex object. > > Thanks, > Nick > >> Subject: Re: StatusLogger >> From: ralph.go...@dslextreme.com >> Date: Mon, 30 Nov 2015 08:30:37 -0700 >> To: log4j-u

Re: StatusLogger

the string. I'm trying to get the original object >> that was passed to one of the logging methods. It could have been a string >> or some complex object. >> >> Thanks, >> Nick >> >>> Subject: Re: StatusLogger >>> From: ralph.go...@dslextreme

RE: StatusLogger

error message"); within the appender I want to "failover" this event to the appender's logger. Is that possible? Thanks, Nick > Subject: Re: StatusLogger > From: ralph.go...@dslextreme.com > Date: Mon, 30 Nov 2015 13:01:23 -0700 > To: log4j-user@logging.apache.org > &

Re: StatusLogger

gt; Ralph >>> >>>> On Nov 30, 2015, at 8:33 AM, Nicholas Duane <nic...@msn.com> wrote: >>>> >>>> I'm not necessarily after the string. I'm trying to get the original >>>> object that was passed to one of the logging methods. It could have

RE: StatusLogger

to be the original object that was logged? Thanks, Nick > Subject: Re: StatusLogger > From: ralph.go...@dslextreme.com > Date: Fri, 20 Nov 2015 12:08:38 -0700 > To: log4j-user@logging.apache.org > > OK - so it sounds like you are fine. > > Ralph > > > > On Nov 2

Re: StatusLogger

municating with > the http endpoint there's not much we can report on that, though I guess we > could write to the StatusLogger at that point. > > I hope I explained it well enough so that you understand what it is we're > trying to do. > > Thanks, > Nick > > > Subject:

RE: StatusLogger

The code happens to be a log4j2 appender, so it sounds like you're saying we should be using the StatusLogger, correct? The issue is that we want to capture the events from our appenders to a central location. Thanks, Nick > Subject: Re: StatusLogger > From: ralph.go...@dslextreme.com

Re: StatusLogger

Maybe we should rename "StatusLogger" to something more "internal" sounding like "CoreLogger" or "InternalLogger"? Gary On Thu, Nov 19, 2015 at 6:01 PM, Ralph Goers wrote: > Yes, the StatusLogger is how Log4j logs things that happen within Log4j > itself. If you are

Re: StatusLogger

int. > > I hope I explained it well enough so that you understand what it is we're > trying to do. > > Thanks, > Nick > >> Subject: Re: StatusLogger >> From: ralph.go...@dslextreme.com >> Date: Fri, 20 Nov 2015 10:16:17 -0700 >>

RE: StatusLogger

> Subject: Re: StatusLogger > From: ralph.go...@dslextreme.com > Date: Fri, 20 Nov 2015 10:16:17 -0700 > To: log4j-user@logging.apache.org > > What do you mean by “capture the events from our appenders”? The > StatusLogger is primarily used during configuration or to log error

RE: StatusLogger

That's what we're doing. The appender it writing to a logger and via the configuration we have that going to this http endpoint. We're careful to ensure that the events raised by our appender don't come back to itself. Thanks, Nick > Subject: Re: StatusLogger > From: ra

Re: StatusLogger

log4j2 appender, so it sounds like you're saying we > should be using the StatusLogger, correct? The issue is that we want to > capture the events from our appenders to a central location. > > Thanks, > Nick > >> Subject: Re: StatusLogger >> From: ralph.go...@dsle

Re: StatusLogger

nsure that the events raised by our appender don't come back to itself. > > Thanks, > Nick > >> Subject: Re: StatusLogger >> From: ralph.go...@dslextreme.com >> Date: Fri, 20 Nov 2015 11:04:57 -0700 >> To: log4j-user@logging.apache.org >> >> You can

Re: StatusLogger

Yes, the StatusLogger is how Log4j logs things that happen within Log4j itself. If you are writing plugins for Log4j those should also use the StatusLogger as they effectively become part of Log4j. If the are regular application code then they should not use the StatusLogger. Although the