[kmcginnes]

Summary

ServerLoggerConnector.debug wrote to the browser console through the info path instead of debug, so debug messages could not be filtered in the console like the other levels.

User-facing: Debug messages now appear under the browser console's Debug level instead of Info.

 public debug(message: string) {
-  this.#clientLogger.info(message);
+  this.#clientLogger.debug(message);
   return this.#sendLog("debug", message);
 }

The request to POST /logger already carried level: "debug" after Send client logs to /logger as a JSON body (#2468), and the proxy already drops it at the default LOG_LEVEL=info, so the server side needs no change.

Evidence

Before: a test for debug expecting logger.debug failed, because the call landed on logger.log.
After: a five-row test.each pins both the console method and the /logger level for error, warn, info, debug and trace, and passes.

Verified live: ran the app against the proxy; debug printed at the console Debug level and was dropped by the server at LOG_LEVEL=info, while info still printed.

Merge Danger

Door: two-way

Impact: negligible

Related

• Related to Send client logs to /logger as a JSON body #2468

---

_{🤖 Written by an AI agent on my behalf.}

[kmcginnes]

Approved