fix(hub): log processing block at debug instead of info - #66
Merged
Merged
Conversation
sduchesneau
reviewed
Sep 10, 2026
Fires per block and per partial. Under WithLogger it escapes bstream=warn log specs and made ~40% of prod log bytes.
Per-block debug hides that the hub is advancing at all; one Info line per 10s restores that without the per-block volume.
GabrielCartier
force-pushed
the
fix/hub-processing-block-debug
branch
from
September 11, 2026 10:02
51e4664 to
89a0546
Compare
maoueh
approved these changes
Sep 15, 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
3 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.
This one log line accounted for roughly 27 GB/day, about 40% of the dfuseio-global project's log ingestion.
hub.ForkableHub.ProcessBlocklogs it once per block, including partial blocks, so on a flash-block chain a relayer emitted around 80 of these lines per block. TheDLOG='.*=info,bstream=warn'spec used in deployments no longer mutes it since firehose-core passes the relayer/firehose logger throughhub.WithLogger, so the line stopped matching thebstream=warnfilter. Dropping it toDebugfixes the ingestion cost without deploy changes.Note:
TestFileSource_Runis flaky (unsynchronizedpreProcessCountread infilesource_test.go), unrelated to this change.