Closed
Bug 1450990
Opened 7 years ago
Closed 7 years ago
Refactor a bunch of the logging config files
Categories
(bugzilla.mozilla.org :: Developer Box, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dylan, Assigned: dylan)
Details
Attachments
(1 file)
I think we want a log4perl log file in the vagrant directory on the developer VM.
What format should it be in? Plain text or the JSON log format we use in production?
|
Assignee | |
Comment 1•7 years ago
|
||
Thoughts on logfile format?
I could do both -- it's not any harder.
Flags: needinfo?(imadueme)
Flags: needinfo?(dkl)
|
|
Assignee | |
Comment 2•7 years ago
|
||
The JSON logs contain a lot more data, so I'm going to just do both.
Flags: needinfo?(imadueme)
Flags: needinfo?(dkl)
|
||
Comment 3•7 years ago
|
||
Plain text would probably be easier to read, but, having logs in the same format as production also makes sense and could help correlate the same problems. Tough decision, I vote for plaintext but that is the lazy side of me speaking.
|
|
Assignee | |
Comment 4•7 years ago
|
||
- provide vagrant logging config
- provide docker-compose logging config
- provide production (json) logging config that logs json to STDERR when cereal.pl is not available
- various other fixes
Summary: Log::Log4perl in the developer VM must log messages to some file → Refactor a bunch of the logging config files
|
|
Assignee | |
Comment 5•7 years ago
|
||
|
|
Assignee | |
Comment 6•7 years ago
|
||
- also no longer logging timings from the apache handler. We have this information from a lot of other sources already
and it makes logs hard to read.
|
|
Assignee | |
Updated•7 years ago
|
Attachment #8966446 -
Flags: review+
|
|
Assignee | |
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•