Re: StatusLogger

[Ralph Goers]

OK - so it sounds like you are fine.

Ralph


> On Nov 20, 2015, at 11:24 AM, Nicholas Duane  wrote:
> 
> 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: ralph.go...@dslextreme.com
>> Date: Fri, 20 Nov 2015 11:04:57 -0700
>> To: log4j-user@logging.apache.org
>> 
>> You can also use a normal logger in your appender for stuff that will happen 
>> at runtime. You just have to be aware that if you have things configured 
>> incorrectly that may result in a loop - at which point Log4j will detect it 
>> and ignore those logging events.
>> 
>> Ralph
>> 
>>> On Nov 20, 2015, at 10:55 AM, Nicholas Duane  wrote:
>>> 
>>> We're attempting to capture error, or info, events that our plugins raise.  
>>> For instance, we wrote a domain sockets appender.  If that domain sockets 
>>> appender has trouble connecting to the domain socket we'd like to know 
>>> about it.  In addition, we'd like to know about it centrally so that we 
>>> don't have to monitor each of the boxes our code is running on.  We 
>>> therefore have a "logging" appender which writes to an http endpoint.  The 
>>> log messages our plugins emit will get forwarded to this logging appender 
>>> (via the configuration) in hopes to get these issues to a central location. 
>>>  Of course if the http appender has trouble communicating 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
 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 errors that 
 occur in the appender. If you are trying to capture the events being 
 logged that sounds a bit odd as that is the purpose of an appender.
 
 If you want to capture all the Log4j status logger output you can specify 
 a destination on the configuration element. The output will then be 
 written to that location instead of to stdout.
 
 Ralph
 
> On Nov 20, 2015, at 8:01 AM, Nicholas Duane  wrote:
> 
> 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
>> Date: Thu, 19 Nov 2015 19:01:45 -0700
>> To: log4j-user@logging.apache.org
>> 
>> 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 StatusLogger uses the same API as the Log4j API its 
>> implementation is quite different and much more limited in what can be 
>> done with the output.
>> 
>> The StatusLogger implementation doesn’t have Appenders. Instead it has 
>> StatusListeners that receive the events. The only listeners provided 
>> with Log4j are the StatusConsoleListener, which writes events to stdout 
>> or a PrintStream, and StatusLoggerAdmin, which makes events available 
>> over JMX.
>> 
>> Ralph
>> 
>> 
>> 
>>> On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
>>> 
>>> I'm trying to get information on the StatusLogger.  I've searched and 
>>> so far the log4j docs say:
>>> 
>>> "Records events that occur in the logging system."
>>> 
>>> There are also a bunch of articles related to people having problems 
>>> with the StatusLogger.  I'm just looking to find out what it is.  It 
>>> appears it's somewhat of an "internal" logger that log4j (log4j2) uses 
>>> to log internal events.  One reason I'm looking into this is because I 
>>> see some code in one of our projects in which the class is logging to 
>>> the StatusLogger.  I assume we shouldn't be doing this.
>>> 
>>> Is the StatusLogger used in log4j2?  In one post I read that the 
>>> "status" attribute controls the level.  Can I set the appender for the 
>>> StatusLogger?
>>> 
>>> Thanks,
>>> Nick
>>>   
>> 
>> 
>> 
>> -
>> To unsub

RE: StatusLogger

[Nicholas Duane]

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: ralph.go...@dslextreme.com
> Date: Fri, 20 Nov 2015 11:04:57 -0700
> To: log4j-user@logging.apache.org
> 
> You can also use a normal logger in your appender for stuff that will happen 
> at runtime. You just have to be aware that if you have things configured 
> incorrectly that may result in a loop - at which point Log4j will detect it 
> and ignore those logging events.
> 
> Ralph
> 
> > On Nov 20, 2015, at 10:55 AM, Nicholas Duane  wrote:
> > 
> > We're attempting to capture error, or info, events that our plugins raise.  
> > For instance, we wrote a domain sockets appender.  If that domain sockets 
> > appender has trouble connecting to the domain socket we'd like to know 
> > about it.  In addition, we'd like to know about it centrally so that we 
> > don't have to monitor each of the boxes our code is running on.  We 
> > therefore have a "logging" appender which writes to an http endpoint.  The 
> > log messages our plugins emit will get forwarded to this logging appender 
> > (via the configuration) in hopes to get these issues to a central location. 
> >  Of course if the http appender has trouble communicating 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
> >> 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 errors that 
> >> occur in the appender. If you are trying to capture the events being 
> >> logged that sounds a bit odd as that is the purpose of an appender.
> >> 
> >> If you want to capture all the Log4j status logger output you can specify 
> >> a destination on the configuration element. The output will then be 
> >> written to that location instead of to stdout.
> >> 
> >> Ralph
> >> 
> >>> On Nov 20, 2015, at 8:01 AM, Nicholas Duane  wrote:
> >>> 
> >>> 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
>  Date: Thu, 19 Nov 2015 19:01:45 -0700
>  To: log4j-user@logging.apache.org
>  
>  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 StatusLogger uses the same API as the Log4j API its 
>  implementation is quite different and much more limited in what can be 
>  done with the output.
>  
>  The StatusLogger implementation doesn’t have Appenders. Instead it has 
>  StatusListeners that receive the events. The only listeners provided 
>  with Log4j are the StatusConsoleListener, which writes events to stdout 
>  or a PrintStream, and StatusLoggerAdmin, which makes events available 
>  over JMX.
>  
>  Ralph
>  
>  
>  
> > On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
> > 
> > I'm trying to get information on the StatusLogger.  I've searched and 
> > so far the log4j docs say:
> > 
> > "Records events that occur in the logging system."
> > 
> > There are also a bunch of articles related to people having problems 
> > with the StatusLogger.  I'm just looking to find out what it is.  It 
> > appears it's somewhat of an "internal" logger that log4j (log4j2) uses 
> > to log internal events.  One reason I'm looking into this is because I 
> > see some code in one of our projects in which the class is logging to 
> > the StatusLogger.  I assume we shouldn't be doing this.
> > 
> > Is the StatusLogger used in log4j2?  In one post I read that the 
> > "status" attribute controls the level.  Can I set the appender for the 
> > StatusLogger?
> > 
> > Thanks,
> > Nick
> >   
>  
>  
>  
>  -
>  To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
>  For additional commands, e-mail: log4j-user-h...@logging.apache.o

Re: StatusLogger

[Ralph Goers]

You can also use a normal logger in your appender for stuff that will happen at 
runtime. You just have to be aware that if you have things configured 
incorrectly that may result in a loop - at which point Log4j will detect it and 
ignore those logging events.

Ralph

> On Nov 20, 2015, at 10:55 AM, Nicholas Duane  wrote:
> 
> We're attempting to capture error, or info, events that our plugins raise.  
> For instance, we wrote a domain sockets appender.  If that domain sockets 
> appender has trouble connecting to the domain socket we'd like to know about 
> it.  In addition, we'd like to know about it centrally so that we don't have 
> to monitor each of the boxes our code is running on.  We therefore have a 
> "logging" appender which writes to an http endpoint.  The log messages our 
> plugins emit will get forwarded to this logging appender (via the 
> configuration) in hopes to get these issues to a central location.  Of course 
> if the http appender has trouble communicating 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
>> 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 errors that 
>> occur in the appender. If you are trying to capture the events being logged 
>> that sounds a bit odd as that is the purpose of an appender.
>> 
>> If you want to capture all the Log4j status logger output you can specify a 
>> destination on the configuration element. The output will then be written to 
>> that location instead of to stdout.
>> 
>> Ralph
>> 
>>> On Nov 20, 2015, at 8:01 AM, Nicholas Duane  wrote:
>>> 
>>> 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
 Date: Thu, 19 Nov 2015 19:01:45 -0700
 To: log4j-user@logging.apache.org
 
 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 StatusLogger uses the same API as the Log4j API its 
 implementation is quite different and much more limited in what can be 
 done with the output.
 
 The StatusLogger implementation doesn’t have Appenders. Instead it has 
 StatusListeners that receive the events. The only listeners provided with 
 Log4j are the StatusConsoleListener, which writes events to stdout or a 
 PrintStream, and StatusLoggerAdmin, which makes events available over JMX.
 
 Ralph
 
 
 
> On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
> 
> I'm trying to get information on the StatusLogger.  I've searched and so 
> far the log4j docs say:
> 
> "Records events that occur in the logging system."
> 
> There are also a bunch of articles related to people having problems with 
> the StatusLogger.  I'm just looking to find out what it is.  It appears 
> it's somewhat of an "internal" logger that log4j (log4j2) uses to log 
> internal events.  One reason I'm looking into this is because I see some 
> code in one of our projects in which the class is logging to the 
> StatusLogger.  I assume we shouldn't be doing this.
> 
> Is the StatusLogger used in log4j2?  In one post I read that the "status" 
> attribute controls the level.  Can I set the appender for the 
> StatusLogger?
> 
> Thanks,
> Nick
> 
 
 
 
 -
 To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
 For additional commands, e-mail: log4j-user-h...@logging.apache.org
 
>>>   
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>> 
> 



-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

RE: StatusLogger

[Nicholas Duane]

We're attempting to capture error, or info, events that our plugins raise.  For 
instance, we wrote a domain sockets appender.  If that domain sockets appender 
has trouble connecting to the domain socket we'd like to know about it.  In 
addition, we'd like to know about it centrally so that we don't have to monitor 
each of the boxes our code is running on.  We therefore have a "logging" 
appender which writes to an http endpoint.  The log messages our plugins emit 
will get forwarded to this logging appender (via the configuration) in hopes to 
get these issues to a central location.  Of course if the http appender has 
trouble communicating 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
> 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 errors that 
> occur in the appender. If you are trying to capture the events being logged 
> that sounds a bit odd as that is the purpose of an appender.
> 
> If you want to capture all the Log4j status logger output you can specify a 
> destination on the configuration element. The output will then be written to 
> that location instead of to stdout.
> 
> Ralph
> 
> > On Nov 20, 2015, at 8:01 AM, Nicholas Duane  wrote:
> > 
> > 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
> >> Date: Thu, 19 Nov 2015 19:01:45 -0700
> >> To: log4j-user@logging.apache.org
> >> 
> >> 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 StatusLogger uses the same API as the Log4j API its 
> >> implementation is quite different and much more limited in what can be 
> >> done with the output.
> >> 
> >> The StatusLogger implementation doesn’t have Appenders. Instead it has 
> >> StatusListeners that receive the events. The only listeners provided with 
> >> Log4j are the StatusConsoleListener, which writes events to stdout or a 
> >> PrintStream, and StatusLoggerAdmin, which makes events available over JMX.
> >> 
> >> Ralph
> >> 
> >> 
> >> 
> >>> On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
> >>> 
> >>> I'm trying to get information on the StatusLogger.  I've searched and so 
> >>> far the log4j docs say:
> >>> 
> >>> "Records events that occur in the logging system."
> >>> 
> >>> There are also a bunch of articles related to people having problems with 
> >>> the StatusLogger.  I'm just looking to find out what it is.  It appears 
> >>> it's somewhat of an "internal" logger that log4j (log4j2) uses to log 
> >>> internal events.  One reason I'm looking into this is because I see some 
> >>> code in one of our projects in which the class is logging to the 
> >>> StatusLogger.  I assume we shouldn't be doing this.
> >>> 
> >>> Is the StatusLogger used in log4j2?  In one post I read that the "status" 
> >>> attribute controls the level.  Can I set the appender for the 
> >>> StatusLogger?
> >>> 
> >>> Thanks,
> >>> Nick
> >>> 
> >> 
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> >> For additional commands, e-mail: log4j-user-h...@logging.apache.org
> >> 
> >   
> 
> 
> 
> -
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
> 
  

Re: StatusLogger

[Ralph Goers]

What do you mean by “capture the events from our appenders”?  The StatusLogger 
is primarily used during configuration or to log errors that occur in the 
appender. If you are trying to capture the events being logged that sounds a 
bit odd as that is the purpose of an appender.

If you want to capture all the Log4j status logger output you can specify a 
destination on the configuration element. The output will then be written to 
that location instead of to stdout.

Ralph

> On Nov 20, 2015, at 8:01 AM, Nicholas Duane  wrote:
> 
> 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
>> Date: Thu, 19 Nov 2015 19:01:45 -0700
>> To: log4j-user@logging.apache.org
>> 
>> 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 StatusLogger uses the same API as the Log4j API its 
>> implementation is quite different and much more limited in what can be done 
>> with the output.
>> 
>> The StatusLogger implementation doesn’t have Appenders. Instead it has 
>> StatusListeners that receive the events. The only listeners provided with 
>> Log4j are the StatusConsoleListener, which writes events to stdout or a 
>> PrintStream, and StatusLoggerAdmin, which makes events available over JMX.
>> 
>> Ralph
>> 
>> 
>> 
>>> On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
>>> 
>>> I'm trying to get information on the StatusLogger.  I've searched and so 
>>> far the log4j docs say:
>>> 
>>> "Records events that occur in the logging system."
>>> 
>>> There are also a bunch of articles related to people having problems with 
>>> the StatusLogger.  I'm just looking to find out what it is.  It appears 
>>> it's somewhat of an "internal" logger that log4j (log4j2) uses to log 
>>> internal events.  One reason I'm looking into this is because I see some 
>>> code in one of our projects in which the class is logging to the 
>>> StatusLogger.  I assume we shouldn't be doing this.
>>> 
>>> Is the StatusLogger used in log4j2?  In one post I read that the "status" 
>>> attribute controls the level.  Can I set the appender for the StatusLogger?
>>> 
>>> Thanks,
>>> Nick
>>>   
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>> 
> 



-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Re: StatusLogger

[Gary Gregory]

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 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 StatusLogger uses the same API as the Log4j API its
> implementation is quite different and much more limited in what can be done
> with the output.
>
> The StatusLogger implementation doesn’t have Appenders. Instead it has
> StatusListeners that receive the events. The only listeners provided with
> Log4j are the StatusConsoleListener, which writes events to stdout or a
> PrintStream, and StatusLoggerAdmin, which makes events available over JMX.
>
> Ralph
>
>
>
> > On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
> >
> > I'm trying to get information on the StatusLogger.  I've searched and so
> far the log4j docs say:
> >
> > "Records events that occur in the logging system."
> >
> > There are also a bunch of articles related to people having problems
> with the StatusLogger.  I'm just looking to find out what it is.  It
> appears it's somewhat of an "internal" logger that log4j (log4j2) uses to
> log internal events.  One reason I'm looking into this is because I see
> some code in one of our projects in which the class is logging to the
> StatusLogger.  I assume we shouldn't be doing this.
> >
> > Is the StatusLogger used in log4j2?  In one post I read that the
> "status" attribute controls the level.  Can I set the appender for the
> StatusLogger?
> >
> > Thanks,
> > Nick
> >
>
>
>
> -
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [ANNOUNCEMENT] Welcome Ralph Goers as the new Apache Logging Chair

[Gary Gregory]

Congratulations Ralph!

Gary

On Fri, Nov 20, 2015 at 7:33 AM, Christian Grobmeier 
wrote:

> Hello all,
>
> I was the chair of the Apache Logging Services project for 3 1/2 years.
> Thank you, it was a great time. But it is time to move on. I think it is
> critical for ASF projects to let the Chair role rotate.
>
> At Logging Services, we agreed to discuss the role each year at the time
> of the ASF members meeting. We did that. We will continue to do that (at
> least that's my hope! :)).
>
> The PMC discussed who could fill the role of the Logging Chair, and
> while we have many great people among us, we unanimously voted for Ralph
> Goers.
>
> Ralph wrote the first versions of what became Log4j 2.0. He wrote large
> parts of it until a fantastic community grew around the project. Without
> him and his hard work, we would still be stuck on Log4j 1.x times when
> things didn't look so bright.
> Ralph is not only an experienced developer but also a great teammate and
> knows the Apache way in and out.
>
> Now I am very happy to say he accepted our vote, and the ASF Board
> confirmed him in his role, effective immediately.
>
> Welcome, Ralph! All the best for your new role, and may the force be
> with you!
>
> Cheers,
> Christian
>
> PS: if you are confused by the terms PMC, Chair or whatever, I'd like to
> invite you to read the blog I posted when I became chair:
> http://www.grobmeier.de/hey-i-became-a-vice-president-07072012.html
>
> Or the official docs:
> http://www.apache.org/foundation/how-it-works.html
>
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [ANNOUNCEMENT] Welcome Ralph Goers as the new Apache Logging Chair

[Paul Benedict]

Congrats Ralph!!!


Cheers,
Paul

On Fri, Nov 20, 2015 at 9:36 AM, Matt Sicker  wrote:

> Welcome, Ralph!
>
> On 20 November 2015 at 09:33, Christian Grobmeier 
> wrote:
>
>> Hello all,
>>
>> I was the chair of the Apache Logging Services project for 3 1/2 years.
>> Thank you, it was a great time. But it is time to move on. I think it is
>> critical for ASF projects to let the Chair role rotate.
>>
>> At Logging Services, we agreed to discuss the role each year at the time
>> of the ASF members meeting. We did that. We will continue to do that (at
>> least that's my hope! :)).
>>
>> The PMC discussed who could fill the role of the Logging Chair, and
>> while we have many great people among us, we unanimously voted for Ralph
>> Goers.
>>
>> Ralph wrote the first versions of what became Log4j 2.0. He wrote large
>> parts of it until a fantastic community grew around the project. Without
>> him and his hard work, we would still be stuck on Log4j 1.x times when
>> things didn't look so bright.
>> Ralph is not only an experienced developer but also a great teammate and
>> knows the Apache way in and out.
>>
>> Now I am very happy to say he accepted our vote, and the ASF Board
>> confirmed him in his role, effective immediately.
>>
>> Welcome, Ralph! All the best for your new role, and may the force be
>> with you!
>>
>> Cheers,
>> Christian
>>
>> PS: if you are confused by the terms PMC, Chair or whatever, I'd like to
>> invite you to read the blog I posted when I became chair:
>> http://www.grobmeier.de/hey-i-became-a-vice-president-07072012.html
>>
>> Or the official docs:
>> http://www.apache.org/foundation/how-it-works.html
>>
>> -
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>
>>
>
>
> --
> Matt Sicker 
>

Re: [ANNOUNCEMENT] Welcome Ralph Goers as the new Apache Logging Chair

[Matt Sicker]

Welcome, Ralph!

On 20 November 2015 at 09:33, Christian Grobmeier 
wrote:

> Hello all,
>
> I was the chair of the Apache Logging Services project for 3 1/2 years.
> Thank you, it was a great time. But it is time to move on. I think it is
> critical for ASF projects to let the Chair role rotate.
>
> At Logging Services, we agreed to discuss the role each year at the time
> of the ASF members meeting. We did that. We will continue to do that (at
> least that's my hope! :)).
>
> The PMC discussed who could fill the role of the Logging Chair, and
> while we have many great people among us, we unanimously voted for Ralph
> Goers.
>
> Ralph wrote the first versions of what became Log4j 2.0. He wrote large
> parts of it until a fantastic community grew around the project. Without
> him and his hard work, we would still be stuck on Log4j 1.x times when
> things didn't look so bright.
> Ralph is not only an experienced developer but also a great teammate and
> knows the Apache way in and out.
>
> Now I am very happy to say he accepted our vote, and the ASF Board
> confirmed him in his role, effective immediately.
>
> Welcome, Ralph! All the best for your new role, and may the force be
> with you!
>
> Cheers,
> Christian
>
> PS: if you are confused by the terms PMC, Chair or whatever, I'd like to
> invite you to read the blog I posted when I became chair:
> http://www.grobmeier.de/hey-i-became-a-vice-president-07072012.html
>
> Or the official docs:
> http://www.apache.org/foundation/how-it-works.html
>
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>
>


-- 
Matt Sicker 

[ANNOUNCEMENT] Welcome Ralph Goers as the new Apache Logging Chair

[Christian Grobmeier]

Hello all,

I was the chair of the Apache Logging Services project for 3 1/2 years.
Thank you, it was a great time. But it is time to move on. I think it is
critical for ASF projects to let the Chair role rotate. 

At Logging Services, we agreed to discuss the role each year at the time
of the ASF members meeting. We did that. We will continue to do that (at
least that's my hope! :)).

The PMC discussed who could fill the role of the Logging Chair, and
while we have many great people among us, we unanimously voted for Ralph
Goers.

Ralph wrote the first versions of what became Log4j 2.0. He wrote large
parts of it until a fantastic community grew around the project. Without
him and his hard work, we would still be stuck on Log4j 1.x times when
things didn't look so bright. 
Ralph is not only an experienced developer but also a great teammate and
knows the Apache way in and out. 

Now I am very happy to say he accepted our vote, and the ASF Board
confirmed him in his role, effective immediately.

Welcome, Ralph! All the best for your new role, and may the force be
with you!

Cheers,
Christian

PS: if you are confused by the terms PMC, Chair or whatever, I'd like to
invite you to read the blog I posted when I became chair:
http://www.grobmeier.de/hey-i-became-a-vice-president-07072012.html

Or the official docs:
http://www.apache.org/foundation/how-it-works.html

-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

RE: StatusLogger

[Nicholas Duane]

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
> Date: Thu, 19 Nov 2015 19:01:45 -0700
> To: log4j-user@logging.apache.org
> 
> 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 StatusLogger uses the same API as the Log4j API its 
> implementation is quite different and much more limited in what can be done 
> with the output.
> 
> The StatusLogger implementation doesn’t have Appenders. Instead it has 
> StatusListeners that receive the events. The only listeners provided with 
> Log4j are the StatusConsoleListener, which writes events to stdout or a 
> PrintStream, and StatusLoggerAdmin, which makes events available over JMX.
> 
> Ralph
> 
> 
> 
> > On Nov 19, 2015, at 6:33 PM, Nicholas Duane  wrote:
> > 
> > I'm trying to get information on the StatusLogger.  I've searched and so 
> > far the log4j docs say:
> > 
> > "Records events that occur in the logging system."
> > 
> > There are also a bunch of articles related to people having problems with 
> > the StatusLogger.  I'm just looking to find out what it is.  It appears 
> > it's somewhat of an "internal" logger that log4j (log4j2) uses to log 
> > internal events.  One reason I'm looking into this is because I see some 
> > code in one of our projects in which the class is logging to the 
> > StatusLogger.  I assume we shouldn't be doing this.
> > 
> > Is the StatusLogger used in log4j2?  In one post I read that the "status" 
> > attribute controls the level.  Can I set the appender for the StatusLogger?
> > 
> > Thanks,
> > Nick
> >   
> 
> 
> 
> -
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>