-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Connect UI to "LiteLLM_DailyUserSpend" spend table - enables usage tab to work at 1m+ spend logs #9603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
… user's usage at 1m+ spend logs Allows user to view their spend at 1m+ spend logs
… if deploy/migrations present in expected location enables easier testing of prisma migration flow
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
… to give breakdowns by provider/model/key
gets to feature parity on 'All Up' page of 'usage.tsx'
… table allows us to see activity by model on new usage tab
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Title
API Request
API Response
Relevant issues
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/
directory, Adding at least 1 test is a hard requirement - see detailsmake test-unit
)[https://docs.litellm.ai/docs/extras/contributing_code]Type
🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test
Changes
Allows user to view their spend at 1m+ spend logs
build(schema.prisma): add api_requests to dailyuserspend table
build(migration.sql): add migration file for new column to daily user spend table
build(prisma_client.py): add logic for copying over migration folder, if deploy/migrations present in expected location
enables easier testing of prisma migration flow
build(ui/): initial commit successfully using the dailyuserspend table on the UI
refactor(internal_user_endpoints.py): refactor
/user/daily/activity
to give breakdowns by provider/model/keyfeat: feature parity (cost page) with existing 'usage' page
build(ui/): add activity tab to new_usage.tsx
gets to feature parity on 'All Up' page of 'usage.tsx'
allows us to see activity by model on new usage tab
style(new_usage.tsx): fix y-axis to be in ascending order of date
fix: fix linting errors
fix: fix ruff check errors