[tor-bugs] #13362 [Onionoo]: Make Onionoo's logs more useful
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Oct 16 10:40:36 UTC 2014
#13362: Make Onionoo's logs more useful
-----------------------------+----------------------------
Reporter: karsten | Owner:
Type: enhancement | Status: needs_revision
Priority: normal | Milestone:
Component: Onionoo | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-----------------------------+----------------------------
Comment (by karsten):
Agreed, let's define what we'd like to log and how, and let's document
that both for code contributors and for service operators. Some
suggestions:
- I'd like to keep a detailed log for debugging problems. We could use
two log levels for normal operation: debug and info.
- There should also be logs for warnings and errors. We might even
suggest setting up Nagios scripts that check whether either of these log
files is not empty and issue a warning message to the operator. During
normal operation, there shouldn't be any warnings or even errors, so we
should only use those two log levels when the operator must take a look.
Once the operator resolves the problem they should delete the log file;
warnings and error messages will still be contained in detailed logs.
We'll probably want two sets of warning/error logs for back-end and front-
end.
- We don't really need a separate statistics log file. What we might
want to do instead is define thresholds for certain operations, like
reading descriptors of a certain time, and emit a warning if that
operation takes longer than that. We could use the same log files as
described above.
I didn't merge my task-13362 branch to master yet. Please let me know
which changes require more discussion, and I'll split up the commit and
merge the undisputed parts.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13362#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list