Skip to content

Stop per-request log spam - #32

Draft
Guardian023 wants to merge 1 commit into
trunkfrom
fix/log-spam
Draft

Stop per-request log spam#32
Guardian023 wants to merge 1 commit into
trunkfrom
fix/log-spam

Conversation

@Guardian023

Copy link
Copy Markdown

Render200 (every response) and /updates endpoint hit (every update) were logging via the always-on Main.Log, producing ~110k of 127k lines in a single Player.log. Route the per-request/response endpoint logs through Main.DebugLog (gated behind settings.enableLogging) instead. Startup, request-exception, and the /ws upgrade diagnostic logs stay always-on. 11 call sites converted.

Render200 fired on every response and "/updates endpoint hit" on every
update, each ~55k lines in a session (110k of 127k log lines total).
Route all the per-request/response endpoint logs through DebugLog
(gated by settings.enableLogging) instead of the always-on Log. Real
logs (startup, request exceptions, the /ws upgrade diagnostic) stay on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant