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?
Thoughts on logfile format? I could do both -- it's not any harder.
The JSON logs contain a lot more data, so I'm going to just do both.
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.
- 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
- 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.
Attachment #8966446 - Flags: review+
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.