You might try using a different Appender (say, a DBAppender) (with an Error threshold, of course) and then sort the resulting tables.
Just log your lines as XML (other formatting will work too of course). This is how we do it: GUIDINVALID_XMLFile x is not in correct xml format Then we parse the log files and show them in a datagridview with a column for errorcode, description, loglevel. We can then quickly sort or filter by, for example ERRORCODE.
Looking in the dataset for those INVALID_XML entries will quickly show us if these errors were present in the logfile. And with the userIds we can also see all the calls that a client did during their login time.
I don't think such a solution exists out of the box. However, you can define a custom log level (or pick one of the unused ones) to output to its own ILog for the more common errors and filter them out on the "main" error log without too much trouble.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.