Problem/Motivation
In the logs, the severity field becomes translated. When analyzing logged data it becomes a problem. It becomes more complicated than it should. Something like ... WHERE SEVERITY IN ("ERROR", "VIRHE", "VIGA", "FEL", "ERRORE", "エラー"). When analyzing logs, or creating alerts, I always use one language. There might be more translated items like this.
Steps to reproduce
- Enable and configure at least one language in addition to English on a site
- Install and configure
jsonlog
- Make sure PHP warnings are logged
- Insert a minor fault anywhere in the codebase like
$a = $b; that triggers "Undefined variable $b".
- Visit some non-English page that triggers that code
- Check the json file. Check the
severity value in the json entry.
Proposed resolution
Do not translate log entries, it's detrimental to analysis.
Remaining tasks
User interface changes
API changes
Data model changes
Comments
Comment #2
ragnarkurm commentedComment #3
robindh commentedComment #5
robindh commentedComment #6
robindh commentedReminder: this might be a breaking change for some systems - create new major version for this.
Comment #7
lorenzs commentedTested on an existing site using JSONLog - severities come in untranslated now as expected.
Rebasing to new version 4.x.
Comment #9
lorenzs commentedComment #10
lorenzs commentedComment #11
lorenzs commented