fix(entitlements): consume endpoint doesn't persist usage events#198
Merged
chitrank2050 merged 7 commits intoMay 27, 2026
Merged
Conversation
- Write usage_event + outbox_event in transaction after Redis increment - Events flow through existing pipeline: outbox → Kafka → aggregation - Ensures consumed usage is durable and reaches billing invoices - Non-blocking: Redis increment is the fast path, DB write is best-effort - Uses consume-endpoint source tag in metadata for traceability Closes #146
chitrank2050
changed the title
chitrank2050
deleted the
fix/146-entitlements-consume-endpoint-doesnt-persist-usage-events
branch
May 27, 2026 11:32
This was referenced May 27, 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
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.
Closes #146