http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660we've experimented with NH before... let me just say there are better options out there. Don't get me wrong its not a horrible system.. but it can be a pain in the ass from time to time. http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment5http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment5Sat, 07 Nov 2009 05:08:55 GMTI find centralized logging as a huge benefit in production. We are using logFaces for doing most of log management stuff and it proves to be great. It aggregates the log data, stores it in separate database, makes log searchable and viewable in real-time. And most importantly - you don't manage the log files, which is a major headache. Whoever needs the log can easily grab it from the database in a snap. This could be a developer, or a support person. http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment4http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment4Fri, 06 Nov 2009 13:09:29 GMTI find one feature extremely useful in production - the ability to reconfigure logging on the fly, without stopping or restarting the application. This way you can turn on more detailed logging if necessary and then return to 'standard' logging. And perfect logging library would allow me to put log statements in source code without stopping the application ;) Up to now I've been able to do that only with scripts and it was good. http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment3http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment3Tue, 03 Nov 2009 18:47:16 GMTApplications that are setup to run and then forgotten about are actually applications that could most stand to have good logs. There should be no "burden" involved in purging the log files. At a minimum, a good logging system will "roll" the log files, ensuring a maximum amount of disk space usage at all times. No need to care that the logs are there... until something happens that you have to diagnose. http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment2http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment2Tue, 03 Nov 2009 14:40:34 GMTMy personal preference is Log4j for Java applications, as it is simple and effective. Have used it in many production environments and no issues till date. http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment1http://ayende.com/4276/what-kind-of-logging-should-you-do-in-production#comment1Mon, 02 Nov 2009 13:51:05 GMT