On a multilingual site we noticed that the logged messages use the translated severity. So for us some messages are logged as "[ERROR]" on the English page and as "[FEHLER]" on the German translation. This makes searching the logs for a specific log severity hard, especially with many languages.
/admin/config/regional/language and set it as the default language.\Drupal::logger()). Make sure that the severity is actually translated for the installed language.To test it I added German as a new language and added \Drupal::logger('test')->warning('test') to Drupal\log_stdout\Form\LogStdoutConfigForm::buildForm(). After visiting /admin/config/development/log_stdout you can see something like ...[WARNUNG] [test] [2024-03-21T11:15:30] test | uid: 1... in the StdOut. When using DDEV you can use ddev logs -f to see the container output.
Use the untranslated severity.
1.5
Code
I've created a MR that uses the untranslated string instead of the translation.
I reviewed the PR8 and can confirm that the messages are now in the untranslated version.
RTBC +1