fix: stream all production logs to stdout/stderr for journalctl

TheLastCicada · TheLastCicada · commit 0adf362cbd27 · 2026-04-20T15:36:51.000-07:00
The previous production Console transport was filtered to error level,
which kept journalctl quiet but left operators who consume logs via
journalctl/pm2/docker without the info/warn context around failures.

Drop the level filter so the transport inherits the logger's configured
level (APP.LOG_LEVEL, default info). Errors still go to stderr via
stderrLevels; everything else goes to stdout. File transports are
unchanged, so the full on-disk log files continue to be written.

Set LOG_LEVEL=debug in CADT config to also stream verbose/debug.
diff --git a/src/config/logger.js b/src/config/logger.js
@@ -117,11 +117,12 @@ const createVersionLogger = (version) => {
       }),
     );
   } else {
-    // In production, mirror error-level logs to stderr so operators can see
-    // them via journalctl/pm2/docker alongside the on-disk log files.
+    // 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.
     versionLogger.add(
       new transports.Console({
-        level: 'error',
         stderrLevels: ['error'],
         format: format.combine(format.json()),
       }),
