Software Logging Schemes

MySkippy writes: "I've been a software engineer for just over 10 years now. I've seen several different styles of logging in the applications I've worked on over the years. Some were extremely verbose containing about 1 logging line per every 2 lines of code. Some were very lacking with maybe 1 logging line for every 200 lines of code. A friend of mine recently turned me on to log4j and log4net and I have begun using both. For logging, I personally find that writing debug and informational messages about every 2 to 5 lines works well for debugging an issue but can become cumbersome when reading through it for analysis. I tend to write warning messages when thresholds or limits are being reached. These tend to be much less in number. I log errors when ever I catch one and I have never put a "fatal" message in my code because if it's truely a "fatal" error that means I probably didn't catch it. After all, if I caught it, it's probably not a "fatal" error. That brings me to my question, what do the slash dotter's out there handle logging in their code?"