Also, that buffer size is configurable and can be controlled on a per-
tab basis.
Also, I just committed a change to ensure the cyclic setting is
persisted.
Scott
On Aug 18, 2010, at 12:47 AM, "Stadelmann Josef" <[email protected]
> wrote:
Hi Team,
I use Chainsaw now, very good. also my colleagues are starting to make
use of it since we integrated it into our overall logging concept.
Maybe there is a littel thing open in our mind. Maybe it's an
oversight
of myself. But I have the following whish.
If the logging event buffer of chainsaw fills up one gets an warning
thate the buffer is ... 75%full ... and up on 100% full will start to
drop logging events.
Why not allowing at this time to send the log events into a file,
maybe
through RollingFileAppender or a DaylyRollingFileAppender in a XML
Format, or just a Format that chainsaw can read it later and we are
able
to analyse length trace sessions from start later, given we have
need of
it?
Sepp
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
