Logging: downgrade high-volume messages to debug - #13212
Draft
ericholscher wants to merge 2 commits into
Draft
Conversation
Reduce logging spam from our most-logged messages. These are all expected, per-build/per-webhook events that aren't actionable at INFO/WARNING level. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HfZV9pHCFW5iU1J7nDt3sd
Keep upload time and per-type artifact sizes visible at INFO for debugging storage slowness and size abuse, in a single log per build. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HfZV9pHCFW5iU1J7nDt3sd
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.
Our most-logged messages (1-day sample) are all expected, per-build/per-webhook events that aren't actionable at INFO/WARNING level. This PR downgrades them to DEBUG, following one rule: state changes and terminal failures stay at INFO; routine "about to do X" markers move to DEBUG.
build_triggered: false+ versions, visible in the provider's webhook delivery UIUnsupported event: <name>uploadingstate in the DB on the next lineMESSAGE_OAUTH_BUILD_STATUS_FAILURE,MESSAGE_OAUTH_WEBHOOK_NO_PERMISSIONS)The artifact size/timing logs kept their INFO-level signal but consolidated: "Store build artifacts finished." now carries the upload
timeand per-typesizesin a single line per build, replacing the separate "Build artifacts directory size." lines. Storage slowness and artifact-size abuse remain debuggable from INFO logs at a third of the volume (~57k → ~18k/day).Not addressed here: "Spam rule matched." (13.9k) and "Show ads denied." (8.35k) come from
readthedocsext.spamfightingand need a matching pass in that repo.Total: roughly 150k log lines/day drop out of INFO.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HfZV9pHCFW5iU1J7nDt3sd
Generated by Claude Code