1450990 - Refactor a bunch of the logging config files

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Developer Box, enhancement)

Description

[Dylan Hardison [:dylan] (he/him)]

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?

Comment 1

[Dylan Hardison [:dylan] (he/him)]

Thoughts on logfile format?

I could do both -- it's not any harder.

Comment 2

[Dylan Hardison [:dylan] (he/him)]

The JSON logs contain a lot more data, so I'm going to just do both.

Comment 3

[Israel Madueme [:imadueme]]

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.

Comment 4

[Dylan Hardison [:dylan] (he/him)]

- 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

Comment 5

[Dylan Hardison [:dylan] (he/him)]

Attachment: PR

Comment 6

[Dylan Hardison [:dylan] (he/him)]

- 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.