fix(web): drop not-found log noise - FINE without stack trace#218
Merged
anderslindho merged 1 commit intomasterfrom May 8, 2026
Merged
fix(web): drop not-found log noise - FINE without stack trace#218anderslindho merged 1 commit intomasterfrom
anderslindho merged 1 commit intomasterfrom
Conversation
A misbehaving client hammering a non-existent channel generated thousands of WARNING entries, drowning out real server-side failures. 404s are client errors; the HTTP response is sufficient, and the audit log already records every lookup at INFO. FINE keeps the messages available under debug logging without polluting production logs.
|
jacomago
approved these changes
May 8, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A misbehaving client hammering a non-existent channel generated thousands of WARNING entries, drowning out real server-side failures. 404s are client errors; the HTTP response is sufficient, and the audit log already records every lookup at INFO. FINE keeps the messages available under debug logging without polluting production logs.