Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #20128

Closed (moved)
Open
Created Sep 10, 2016 by iwakeh iwakeh@iwakeh

Make CollecTor operators aware of logging

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}.jars 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 (moved) will be avoided.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None