Implement client side logging and log retrieval

[GoogleCodeExporter]

We need a way to see the failure states that occur on remote clients that
we do not have access to.  Since there are several failures that we don't
seem to be able to reproduce locally, having users be able to submit their
logs is important.

Original issue reported on code.google.com by stephen....@gmail.com on 16 Dec 2009 at 8:26

[GoogleCodeExporter]

Original comment by stephen....@gmail.com on 4 Jan 2010 at 8:30

• Added labels: Milestone-Release0.7.5

[GoogleCodeExporter]

Thanks Dave for the great presentation today.  Slides are posted here:

http://docs.google.com/present/view?id=dzxg4cx_6h3vc3hcj

Example demo code is available here:

http://code.google.com/p/wholebrain/source/browse/#svn/logging-demo

Original comment by stephen....@gmail.com on 13 Jan 2010 at 2:57

[GoogleCodeExporter]

More specifically now, we should address where we need logging the most 
earnestly.  I 
think going through the start up sequence and converting our current logging 
statements 
into slf4 statements would be a good start.  We probably need to add more of 
them as 
well.  We should implement the log4j.properties file from dave's example in WBC 
and 
make sure we have logging to a file working correctly.  Then lets evaluate if 
we are 
getting good complete logs out that can adequately describe the failure states 
we have 
experienced.  We can reference a WBC architecture meeting from several weeks 
ago where 
I outlined the failure states on the board.  I am attaching a picture from that 
board.

Original comment by stephen....@gmail.com on 13 Jan 2010 at 3:02

Attachments:

• CIMG0630.jpg

[GoogleCodeExporter]

As I said today my knowledge of logging is somewhat narrow based on particular
situations with which I've been confronted in the past, but I hope I helped get 
the
ball rolling. I suggest a peek at 
http://n3.nabble.com/How-to-programmatically-set-log-level-in-SLF4J-td45652.html
for an interesting discussion. The last signature is that of Ceki Gulcu whose 
name I
see a lot in connection with logging--especially log4j (I think he wrote the 
book)
and slf4f (he may have invented it) and now "logback" with which I'm not 
familiar.

The discussion talks about the logging API v. the underlying logging package 
(slf4j
and log4j in my presentation). Considering the programmatic configuration and 
the
fact that WBC client is an "end" development, maybe it makes better sense to use
log4j directly or logback which Ceki mentions.

(This all sounds familiar to JPA v. Hibernate in which we use the JPA API with
Hibernate as the underlying implementation.)

Original comment by davlit0...@gmail.com on 13 Jan 2010 at 4:29

[GoogleCodeExporter]

Appears to be working.  Log file ends up in user's home directory as wbc.log.

Original comment by stephen....@gmail.com on 26 Jan 2010 at 6:58

• Changed state: Fixed