Opened 9 years ago

Last modified 3 years ago

#5241 new enhancement

Log location at DEBUG / INFO level

Reported by: atagar Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client logging tor-control machine-readable
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


During the dev meeting I mentioned to Roger that a log message identifier would help me to deduplicate log messages with dynamic content.

Roger made the counter proposal that at high runlevels (NOTICE and above) any noisy logging is a bug and at low runlevels (DEBUG and INFO) we could log the file and line number where the logging occurred. This would both help with tracing through the code and also be something that I could use for deduplication.

Cheers! -Damian

Child Tickets

Change History (4)

comment:1 Changed 9 years ago by nickm

Milestone: Tor: unspecified

Either idea seems ok-ish to me. If there were unique identifiers, I would want an automated way to assign them and keep them unique. If it were file and line number, I would be a little annoyed by the fact that I would need to know which version generated a message to actually trace that back.

comment:2 Changed 8 years ago by nickm

Keywords: tor-client added

comment:3 Changed 8 years ago by nickm

Component: Tor ClientTor

comment:4 Changed 3 years ago by nickm

Keywords: logging tor-control machine-readable added
Severity: Normal
Note: See TracTickets for help on using tickets.