Hi Kris,

I might be wrong, but I think such an appender already exists in the log4j
framework?  I know I have heard this one before...

At any rate, if you are willing to apply an Apache license to the source
code, we can certainly move the appender into the log4j-sandbox, and given
time, documentation, and test cases, possibly move it into the log4j core at
some point.

-Mark

----- Original Message ----- 
From: "kris wehner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 26, 2003 5:18 PM
Subject: Question about submitting a new appender


> Hi All --
>
> I'm new to the list, and have a few questions about code contributions
> and what is generally included in the log4j core versus maintained
> externally.
>
> I developed an appender that scratches a particular itch I have, which
> is the performance penalty of writing large amounts of logging data
> during development. The problem being that a fully instrumented app will
> write megs and megs of audit data (with logger.*=DEBUG), causing it to
> slow down a LOT due to pure I/O. Generally, I'm only interested in the
> last 1000 or so messages before a crash, making the I/O time wasted and
> writing a TON of log data that has to be waded through. My appender
> wraps the rolling file appender, and pushes the audit data into a
> (configurable) fixed size ring buffer that can be dumped via a simple
> user interface. This allows the user to go "oh, something happened, let
> me look at the debug output" without having to grep through 20 megs of
logs.
>
> I am planning on releasing the code under the apache license, and would
> be more than happy to contribute it to the project or keep it as a
> separate module on sourceforge, depending on the wishes of the
maintainers.
>
> Kris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to