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:
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
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
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
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
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
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
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
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:
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
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
11 matches
Mail list logo