I'd try to understand why he wants this. Is it for metric reporting instead of operations? It might make sense then (although I'd say it's a poor measure, but better than nothing).
If it is for metrics, then write everything to a single file and parse it after for his metrics. Point out that operationally, the log is far more valuable for support if you can see the thread of events in context of time - which may not correspond to the separate levels. Also, operationally, does he expect you to run your app with debug logging on at all times? We, and I think most people, may have debug on in QA and perhaps right after go-live, but once you know it is stable, throttle back to WARN or INFO. So depending on the scenario, he might not get what he is expecting anyway. If what he is after is reporting, then generate one log and parse it for him at the end of each day (or whenever you do your rollover.) Erik -----Original Message----- From: Charles Johnson [mailto:[EMAIL PROTECTED] Sent: Friday, June 24, 2005 10:20 AM To: log4net-user Subject: Log file for each level Doesn't sound like a brilliant idea to me, but my manager wants me to produce a separate log file for each log level and i was wondering what the best way to do this is? CJ DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
