Open
Bug 1369948
Opened 7 years ago
Updated 2 years ago
Use 'rotate' by default in about:network HTTP logging
Categories
(Core :: Networking, enhancement, P3)
Core
Networking
Tracking
()
NEW
People
(Reporter: jduell.mcbugs, Unassigned)
Details
(Whiteboard: [necko-triaged])
There are times when we'll be telling people to turn on logging and browse around for a not-easily reproducible bug, and those folks will benefit from having rotate on by default. And it shouldn't hurt people who have easy STR--their logs are unlikely to need to be more than a few MB anyway. Bonus points: pick a rotate log size that's either less than the max Bugzilla attachment size (which I don't actually know), or statistically is very likely to compress to that size.
Reporter | ||
Comment 1•7 years ago
|
||
I suspect Valentin could knock this off the most quickly.
Flags: needinfo?(valentin.gosu)
Comment 2•7 years ago
|
||
(In reply to Jason Duell [:jduell] (needinfo me) from comment #0) > There are times when we'll be telling people to turn on logging and browse > around for a not-easily reproducible bug, and those folks will benefit from > having rotate on by default. And it shouldn't hurt people who have easy > STR--their logs are unlikely to need to be more than a few MB anyway. > > Bonus points: pick a rotate log size that's either less than the max > Bugzilla attachment size (which I don't actually know), or statistically is > very likely to compress to that size. No. Let them zip it, all the time (could we add a zip feature?). The size should be, when there is also the nsSocketTransport:5 module active, at least 500MB or even more. Note that child logs will never go over few megabytes.
Comment 3•7 years ago
|
||
From what I recall, the rotate option was left out because it would have seriously complicated the implementation - races, etc. I think we could implement it, either in Logging.cpp or in the NetworkingDashboard in JS, but I don't know at the moment how difficult that would be. (In reply to Honza Bambas (:mayhemer) from comment #2) > No. Let them zip it, all the time (could we add a zip feature?). The size > should be, when there is also the nsSocketTransport:5 module active, at > least 500MB or even more. Note that child logs will never go over few > megabytes. Zipping would indeed be a useful feature. There's lots of improvement room for this tool.
Flags: needinfo?(valentin.gosu)
Comment 4•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P2
Updated•5 years ago
|
Priority: P2 → P3
Whiteboard: [necko-next] → [necko-triaged]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•