feat(memory): wire usage_events table from dispatcher#2431
Merged
alekspetrov merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
The usage_events table was provisioned and the metering writers were implemented, but no production code emitted events — leaving the billing/per-user-cost pipeline dead. The dispatcher worker now calls RecordTaskUsage after persisting execution metrics so each completed execution emits task + token + compute events. Also adds a UserID field to Execution for future multi-tenant rollups; empty in single-tenant deployments.
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
2 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.
Summary
RecordTaskUsageafterSaveExecutionMetrics, emitting task + token + compute events intousage_eventsfor every completed execution.UserIDfield to theExecutionstruct as the pivot for future multi-tenant cost rollups (empty in single-tenant deployments).Closes GH-2429.
Test plan
go build ./...go test ./internal/memory/... ./internal/executor/...SELECT * FROM usage_events ORDER BY timestamp DESC LIMIT 5— expect 3 rows per execution.