Hello again to the log4net group! I am currently using L4N to log all the errors in a real time data acquisition application and have come across a bit of a problem. There are certain places in the application where exceptions occur at a very high rate when a problem does arise and the log files generated become huge in a matter of minutes (or in one case, seconds). The specific places that I have found this to be problematic is in a serial driver and in the class that stores the data to a database.
Although L4N can limit the size of the files and the number of "roll overs", I (read "My Boss") would also like to limit the rate at which these exceptions are actually logged. Is there any built in mechanism that I can use to achieve this? I would still like to know that the errors are occurring, but in the cases that I am thinking of, I don't need to know that one or two exceptions occurred 35 times in one second! I am looking at implementing some sort of "buffer" that holds the past x errors and has a threshold that defines the time period between exceptions logged, but again, I was wondering if there was anything internal to L4N to achieve this? I'm well aware that I need to eliminate the problematic exceptions, but I still need to have some mechanism to find out when they occur. In the case of the serial driver, it has been running very well but the other day I tried using a Serial to USB dongle (converter) that caused problems. I have since eliminated that specific problem, but as I'm sure everyone is aware, these things are not always foreseeable. Any suggestions would be greatly appreciated. Thank you once again for your help. Sincerely, Russell Haley
<<attachment: winmail.dat>>
