[tor-bugs] #20128 [Metrics/CollecTor]: Make CollecTor operators aware of logging
    Tor Bug Tracker & Wiki 
    blackhole at torproject.org
       
    Wed Sep 14 07:20:20 UTC 2016
    
    
  
#20128: Make CollecTor operators aware of logging
-------------------------------+-----------------------------------
 Reporter:  iwakeh             |          Owner:
     Type:  enhancement        |         Status:  needs_information
 Priority:  Medium             |      Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |        Version:
 Severity:  Normal             |     Resolution:
 Keywords:                     |  Actual Points:
Parent ID:                     |         Points:
 Reviewer:                     |        Sponsor:
-------------------------------+-----------------------------------
Changes (by iwakeh):
 * status:  new => needs_information
Old description:
> The logging framework configuration should be decoupled from CollecTor,
> i.e.
>
> * remove default logback.xml from `collector-<version>.jar`
> * add an example of logback.xml to src/main/resources
> * provide the two `logback-{classic,core}.jar`s with a release, but
> remove them from `collector-<version>.jar`
> * add more logging info to the operating guide
>
> The goal should be to make operators aware of the logging choices and
> their responsibilities.  Without a default logging setup operators will
> have to think about choices like
>
> * logging framework implementation
> * log-level settings
> * logging environment, e.g. path settings etc.
>
> Once an instance is configured these logging settings won't just change
> magically and thus issues like #20079 will be avoided.
New description:
 The logging framework configuration should be decoupled from CollecTor,
 i.e.
 * remove default logback.xml from `collector-<version>.jar`
 * add an example of logback.xml to src/main/resources
 * provide the two `logback-{classic,core}.jar`s with a release, but remove
 them from `collector-<version>.jar`
 * add more logging info to the operating guide
 The goal should be to make operators aware of the logging choices and
 their responsibilities.  Without a default logging setup operators will
 have to think about choices like
 * logging framework implementation
 * log-level settings
 * logging environment, e.g. path settings etc.
 Once an instance is configured these logging settings won't just change
 magically with the upgrade to a new release and thus issues like #20079
 will be avoided.
--
Comment:
 Added missing phrase and set to needs-info.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20128#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
    
    
More information about the tor-bugs
mailing list