Agreed. Through what I have found is that there is little agreement on how
much logged information to too much and falls into debugging territory (let
alone what it is). I tend to lean to less is better because it's easier to
see real error messages and exceptions. Others lean toward as much
information as possible so I can understand what this is doing. Both are
valid approaches that serve completely opposite needs. So, I would suspect
this is tied up in that quandary.
Andy
-----Original Message-----
From: Jacek Becla
Sent: Wednesday, April 29, 2015 11:34 AM
To: qserv-l
Subject: [QSERV-L] logging: debug vs info
I noticed we use "info" in very many places, where I think we really
mean "debugging". A quick look on the web clearly shows many people
get confused. I tried to think about how to draw the line, how about this:
INFO
* provides a "storyline" of normal application
* typically turned on in production
DEBUG
* turned on temporarily in dev environment to
debug a problem, or help with development new code
Jacek
p.s. I think that discussion might be better placed in
[log in to unmask], but I figured let's agree among
ourselves first
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
