Sends billing.events log lines to S3 - #2522
Open
Hazel-Datastax wants to merge 58 commits into
Open
Conversation
Contributor
📈 Unit Test Coverage Delta vs Main Branch
|
Contributor
Unit Test Coverage Report
|
Hazel-Datastax
marked this pull request as ready for review
July 16, 2026 21:49
Hazel-Datastax
changed the title
billing.events log lines to S3
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.
What this PR does:
Sends
billing.eventslog lines to S3 as batched NDJSON objectsHow it works:
BillingS3HandlerInstallerwires it up: attachesBillingS3LogHandlerto thebilling.eventsJUL logger at startup, detaches/closes it at shutdown.BillingS3LogHandleris the orchestrator.publish()pushes each line intoBillingQueue; the handler then decides when to ship — batch sealed (count/bytes), age tick, orclose()drain — gates upload concurrency, calls the uploader, and records outcomes viaBillingMetrics. Delivery is at-most-once by design: publish never blocks on S3, a full queue drops events, shutdown drains best-effort within a timeout.BillingQueueowns the batching policy (seal by max events/bytes) and hands out drained batches.S3BatchUploaderis the only S3-aware piece (AsyncBatchUploaderimpl) — encodes NDJSON, PUTs to a time-partitioned key.BillingMetricstracks offered/flushed/failed/dropped counts plus a delivery heartbeat.Tests
BillingS3LogHandlerTestis the main coverage: per-method unit tests (flush triggers, failure containment, close draining), plus concurrency tests (multi-producer no-loss/no-dup, close racing with in-flight publish) and pipeline tests (concurrency gate, auto-chaining the next batch on settle).BillingS3ExportIntegrationTestcovers the real path end-to-end against S3Mock, including that a dead S3 endpoint never breaks the API.Which issue(s) this PR fixes:
Fixes #
Checklist