feat(telemetry): persist LLM token usage in the database - #612
Merged
haiphucnguyen merged 1 commit intoAug 7, 2026
Merged
Conversation
- Store individual LLM usage records for durable token and call statistics - Expose repository-backed usage summaries by time period and model - Refactor telemetry collection and UI to consume persisted usage data - Update exports and dependency injection for database-backed telemetry - Remove obsolete in-memory persistence and RAG telemetry coupling - Add repository tests for LLM usage persistence
|
|
haiphucnguyen
approved these changes
Aug 7, 2026
haiphucnguyen
left a comment
haiphucnguyen
left a comment
Collaborator
There was a problem hiding this comment.
Thank you @GurreXr ! Looking forward to your next PR
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
3 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.
Ref: #603