Hi Joe, There is currently nothing in log4net that behaves similar to this.
Generally said, it is bad design to depend on buffering large amounts of data. If a user really goes into error state and produces large amounts of log messages before the server detects that he should write those messages to the persistency, there are two things the server can do: * cache only a fixed number of messages and dropping the oldest ones but also risking to loose important information * buffer everything and risking a denial of service because of memory bottlenecks due to the large amount of messages being buffered Therefore the way I see it, it is probably the best way to log everything to some persistency and purge unwanted stuff later. You could, for example, log everything to a database and purge unwanted rows with a cron job that runs every 12 hours. Cheers >-----Original Message----- >From: Joe Udwin [mailto:[email protected]] >Sent: Monday, August 13, 2012 5:02 PM >To: Log4NET User >Subject: RE: Lossy logging on a per user basis for a high traffic website > >Hi Dominik, > >Thanks for your reply. >I am trying to do option 2. I would like to buffer the logs for a >particular request and only output them if an exception occurs. >However, I would only want to output logs related to that request, so in my >head I need a buffer per request but perhaps there is a more performant way >to handle this in log4net?
