Demote per-vCon hot-path INFO logs to DEBUG (CON-763) - #199
Merged
Conversation
At BDS volume the per-link and per-vCon progress lines emit ~5,000 log lines/s (38 GiB/day into SigNoz ClickHouse), 3M INFO lines per 10 minutes against ~1 warning. Keep one INFO summary per vCon (Completed processing vCon ... in N seconds) and all anomaly lines (halt, DLQ, skip); demote the rest of the routine progress lines to DEBUG. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
At XXX volume the conserver's per-link/per-vCon progress logging emits ~5,000 lines/s — 38 GiB/day of ClickHouse storage in SigNoz, and a 3,090,000:1 INFO-to-WARNING ratio per 10 min. The signal is all in metrics and spans already (
conserver.link.count, link/vCon timing histograms, per-link spans).This keeps exactly one INFO line per vCon (
Completed processing vCon ... in N seconds, which carries the timing extras) plus every anomaly line (chain halt, DLQ move, before_processing skip), and demotes the routine progress lines to DEBUG:Processing link/Completed link(per link — the bulk of the volume)Processing tracer/Completed tracerStarted processing vCon,Forwarding vCon to egress,Saving vCon to storage backends,Completed chain,Completed parallel storage writesQueue status(fires once per dequeued vCon)Expected effect at XXX: log volume drops ~97% with no loss of ops signal. Note
LOG_LEVELenv is read in settings.py but never applied — the effective config iscommon/logging.conf(root INFO), so DEBUG lines stop being emitted with no other change.🤖 Generated with Claude Code