Repository navigation
Expose volatile ingest buffers and delivery outcomes - #94
Merged
Merged
Conversation
This was referenced Nov 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
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.
Accepted ingest rows can remain in the in-memory batcher while ClickHouse or the durable spool is unavailable. Add per-table pending rows/bytes/age and blocked-flush gauges, plus delivery outcomes, rows, latency and insert failures. A separate atomic sampler keeps backlog age visible while a flush holds its mutex; cancelled attempts do not count as successful delivery.
Validation: 15 writer tests passed, including failed flush/recovery and cancellation metrics; full library suite passed (787 passed, 14 integration tests ignored). cargo fmt --check and cargo clippy --all-targets passed. Strict clippy -D warnings remains blocked by existing repository warnings. Labels are fixed table/outcome values; no tenant identifiers are emitted.