[metrics-bugs] #33549 [Metrics]: Simplify logging configuration across code bases
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Mar 8 08:05:08 UTC 2020
#33549: Simplify logging configuration across code bases
-----------------------------+----------------------
Reporter: karsten | Owner: karsten
Type: enhancement | Status: assigned
Priority: Medium | Milestone:
Component: Metrics | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
-----------------------------+----------------------
We're using different logging configurations in our code bases, some of
which are broken and others are more complex than we need them to be. Some
examples:
- CollecTor has a shutdown console logger, but it's not being printed to
anymore since we refactored package names.
- CollecTor has five separate log files for the modules that existed back
when we added those log files, but these are not being written to since we
refactored package names. We also added more modules but did not update
the logging configuration for them.
- Onionoo and a few others have a separate error log file which logs only
ERROR messages, but we're not doing anything with that file.
- Some code bases have a separate statistics log file that we likewise do
not pay any attention to.
- All code bases rotate log files whenever they reach a size of 1 MiB,
but they do not restrict the number or total size of log files being
written. It would be easier to handle 1 file per day even if that grows to
100 MiB or more.
- There could be a more reasonable default for the log directory than
`LOGBASE_IS_UNDEFINED`.
- It would be convenient to be able to configure the log level that
doesn't require providing a full logging configuration, like
`-DLOGLEVEL=DEBUG`.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33549>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the metrics-bugs
mailing list