perf(observability): bound log flushing and retries - #185
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
size:L
vouch:trusted
badcuban
force-pushed
the
perf/t3-learnings
branch
from
August 24, 2026 19:07
d1bf7c0 to
5ab5e2d
Compare
badcuban
force-pushed
the
perf/t3-learnings
branch
from
August 24, 2026 19:24
5ab5e2d to
3b0e0b0
Compare
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.
Provider-event and trace loggers kept periodic flush loops alive while idle, used record-count batching, and could retry failed disk writes from hot paths. Partial failures could also retain too much data or retry chunks that had already succeeded.
Flush only when work is pending, account for UTF-8 bytes, chunk writes on complete NDJSON records, and bound retained data. Failed writes now recover through owned timers with capped exponential backoff; provider buffers share one logger-wide byte budget, and oversized records are dropped before sink I/O.
Verification: