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

  1. Enable and configure at least one language in addition to English on a site
  2. Install and configure jsonlog
  3. Make sure PHP warnings are logged
  4. Insert a minor fault anywhere in the codebase like $a = $b; that triggers "Undefined variable $b".
  5. Visit some non-English page that triggers that code
  6. 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

Issue fork jsonlog-3314848

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

ragnarkurm created an issue. See original summary.

ragnarkurm’s picture

Issue summary: View changes
robindh’s picture

Assigned: Unassigned » robindh

robindh’s picture

Status: Active » Needs review
robindh’s picture

Reminder: this might be a breaking change for some systems - create new major version for this.

lorenzs’s picture

Tested on an existing site using JSONLog - severities come in untranslated now as expected.
Rebasing to new version 4.x.

lorenzs’s picture

Status: Needs review » Reviewed & tested by the community
lorenzs’s picture

Version: 3.0.0 » 4.x-dev
Assigned: robindh » Unassigned
Issue tags: +VDAB-open-sprint-22
lorenzs’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.