Opened 8 years ago

Last modified 2 years ago

#5287 new enhancement

Turn LogMessageDomains on by default?

Reported by: rransom Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client
Cc: atagar, chiiph Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I keep forgetting to turn on LogMessageDomains when collecting verbose logs. That option should make the resulting logs easier to filter and otherwise grep.

Should it be turned on by default? Should we add a third state to the option so that it can be turned on by default for lower-than-notice-level messages?

(CCing atagar and chiiph, because they maintain software that parses parts of log messages.)

Child Tickets

Change History (9)

comment:1 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

I am in favor of doing this in 0.2.4.x. I hope that atagar or chiiph objects before I merge the patch, not after. :)

comment:2 Changed 7 years ago by nickm

Keywords: tor-client added

comment:3 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:4 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

comment:5 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:6 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:7 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:8 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:9 Changed 2 years ago by nickm

Priority: MediumLow
Severity: Normal

This is trivial to do if people decide they want it.

Note: See TracTickets for help on using tickets.