fix: use silly level on production Console transport

TheLastCicada · TheLastCicada · commit 0f54cc606fa6 · 2026-04-21T14:14:16.000-07:00
Winston 3 treats a transport's `level` independently from the logger's
level -- the logger's level is only the default for transports that
don't specify their own. Without setting a level on the new production
Console transport, it inherited the logger's level (APP.LOG_LEVEL,
default info), so verbose/debug lines never reached journalctl even
though the existing debug-%DATE%.log file captured them.

Set `level: 'silly'` on the Console transport so journalctl receives
every log line the app emits, regardless of APP.LOG_LEVEL. File
transports are untouched.
diff --git a/src/config/logger.js b/src/config/logger.js
@@ -118,11 +118,18 @@ const createVersionLogger = (version) => {
     );
   } else {
     // In production, also stream every log line the logger emits to the
-    // process's stdout/stderr so operators can consume them via journalctl,
-    // pm2, or docker. File transports above continue to hold the same data
-    // on disk. Errors go to stderr, everything else to stdout.
+    // process's stdout/stderr so operators can consume the full log stream
+    // via journalctl, pm2, or docker. File transports above continue to
+    // hold the same data on disk. Errors go to stderr, everything else to
+    // stdout.
+    //
+    // NOTE: in winston 3 a transport's `level` is independent of the
+    // logger's level, so we explicitly use 'silly' (the most permissive
+    // level) to guarantee that anything the app logs reaches journalctl,
+    // regardless of APP.LOG_LEVEL.
     versionLogger.add(
       new transports.Console({
+        level: 'silly',
         stderrLevels: ['error'],
         format: format.combine(format.json()),
       }),
