[tahoe-lafs-trac-stream] [tahoe-lafs] #1936: the tahoe-lafs logging system is hard to discover

[tahoe-lafs]

#1936: the tahoe-lafs logging system is hard to discover
------------------------------+--------------------------------------------
     Reporter:  zooko         |      Owner:
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-         |    Version:  1.9.2
  nodeadmin                   |   Keywords:  usability transparency logging
   Resolution:                |
Launchpad Bug:                |
------------------------------+--------------------------------------------

Comment (by gdt):

 Replying to https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1936#comment:8:

 What I would expect is for tahoe to use the
 LOG_{DEBUG,INFO,NOTICE,WARNING,ERR} hierarchy from syslog.h, and for most
 of the current logs to be DEBUG.   INFO might be peer connections coming
 and going, and perhaps NOTICE for the introducer.  Then people can
 configure syslogd appropriately for what they want.   So piping flogtool
 to logger fails to label messages with priority level.  And then there's
 assessing what logs make sense for routine operations when nothing is
 known to be wrong.   (Presumably fetching files when all works ok is not
 noteworthy.)

 One thing I noticed about flogtool is that when starting it, the past is
 apparently in the past, and not accessible.  That sort of makes sense, but
 it somewhat defeats the purpose of logging.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1936#comment:10>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage