Should the below work for the SmtpAppender? I am using log4net 1.2.10, and it
just shows [P{log4net:HostName}] test in the subject instead of the hostname.
subject type=log4net.Util.PatternString
conversionPattern value=[%P{log4net:HostName}] test/
/subject
Subject: Re: batching log entries until exception
Should the below work for the SmtpAppender? I am using log4net
1.2.10, and it just shows [P{log4net:HostName}] test in the subject
instead of the hostname.
subject type=log4net.Util.PatternString
a basic one that I wrote based on the mailing list posting.
--Brian
-Original Message-
From: Walden H. Leverich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 27, 2007 9:44 AM
To: Log4NET User
Subject: RE: batching log entries until exception
Writing log events to an appender
]
To: Log4NET User log4net-user@logging.apache.org
Sent: Wednesday, November 28, 2007 4:36:10 PM
Subject: RE: batching log entries until exception
What I wouldn't give for a
lower-than-debug logging level. :)
Log4net supports several more levels than the standard 5 (fatal, error,
warn, info, debug
David Bicking wrote:
Hello,
I searched the list for this information, but I think my use case is a bit
obscure. I am researching Log4Net as a possible plug-in logger for our
software. We would like to have or create an unusual feature.
We would like to collect log entries in
You could store a list or CyclicBuffer in the HttpContext then write an
HttpModule that flushes the events when appropriate. If you use a CyclicBuffer
you can set it so the message count doesn't exceed a certain number. I recall
there being some discussion about writing code that would capture
is said in Latin seems profound.)
-Original Message-
From: Ron Grabowski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 27, 2007 12:40 PM
To: Log4NET User
Subject: Re: batching log entries until exception
You could store a list or CyclicBuffer in the HttpContext then write
