Disqus - Latest Comments for tfnico

Re: Alt kan refaktoreres

tfnico — Sun, 24 May 2009 10:47:45 -0000

Nydelig!

Re: Architecture as tidying up

tfnico — Thu, 05 Feb 2009 03:16:13 -0000

Good thought, Johannes. I was just struggling with this yesterday, I was adding a JDBC implementation of an interface inside a functional package "picture.storage" ,and suddenly I found myself having to increase the visibility of several implementation methods to public so I could use them in the "dao.jdbc" package. Very booring.

Re: Verbose logging will disturb your sleep

jhannes — Sat, 01 Nov 2008 10:29:02 -0000

Cool. 'Nuff said.

Re: Verbose logging will disturb your sleep

tfnico — Fri, 31 Oct 2008 20:19:56 -0000

Well, it is an alternative for us to use SEVERE for waking us up in the night. I feel FATAL is like the last thing that might get logged before a java.lang.Error gets thrown and the JVM dies.

All in all it's very important that every team decides how they are going to use the log levels, and follow these conventions throughout project and maintenance.

Re: Verbose logging will disturb your sleep

jhannes — Fri, 31 Oct 2008 14:12:53 -0000

I'm starting to wonder: Is it just me, or are we all neglecting the "SEVERE/FATAL" error category. Should we use it more?

Re: Verbose logging will disturb your sleep

tfnico — Fri, 31 Oct 2008 11:18:51 -0000

Good idea. I'll try to get something like that in. Currently our use of WARN is more or less the same as DEBUG :)

New record yesterday, only 17 errors in the log! \o/

Re: Verbose logging will disturb your sleep

jhannes — Thu, 30 Oct 2008 16:17:29 -0000

Very cool case. Another nail in the SOA coffin. ;-)

What is the consequence of one such hiccup? If there is some chance that manual intervention is needed, I would log this as ERROR. If there is a sufficient compensation (a retry algorithm, say), I would log this as INFO, and log a permanent failure as ERROR. ERROR messages "wake me up in the middle of the night".

If it's in between (e.g. the user got an error message, but no manual intervention is needed) I would log as WARN and collect errors like you do. Knowing me, I would perhaps even keep track of this in the application database, but that's probably gold plating. WARN messages don't wake me up in the middle of the night.

Re: Verbose logging will disturb your sleep

tfnico — Thu, 30 Oct 2008 09:39:20 -0000

My problem is that I have many different kind of errors. Since I'm lucky enough to live in a SOA world, I'm using 10 different service providers that each have a handful of hickups per day, and therefore my log-file has about 25-50 new lines each day (still small enough to manage with tail, I think).

What I do today is manually count number of errors from each service and store them in an excel sheet. Over time I judge which error is critical enough to do something about. Since we started doing this we've gone from 500 log-errors/day to 50/day.

It would be nice to have some better reporting based on exception type and cron-jobs that could fill in the excel sheet for me, but cost/value (I'm a lousy scripter and our exception structure is kind of chaotic) still makes excel/manual counting the best choice. What you think I should do?

Re: I'm moderating the IfI alumni open source debate

tfnico — Fri, 24 Oct 2008 06:55:09 -0000

Thanks for the re-tweeting. Erm, re-blogging.