Adds Fumadocs coverage for the Usage feature - #115
Closed
MSami625 wants to merge 35 commits into
Closed
Conversation
…3 artifacts on preview
…and actor stamping
…oved task dispatching
…ics across services
… for usage features
…tion in Docker and API
…rocess_evaluator_result.py
…ing and cache/Ui fixes
…r available models
…iguration for periodic job scheduling
…R(255) and add migration function
…on to clear cache before seeding pricing rates
…sage pricing routes; enhance usage snapshot billability checks
…eamline cost calculations for pending usage deltas
…ed references in the documentation
|
Too many files changed for review (162 files, 100 file limit). Bypass the limit by tagging |
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
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 Changed?
Adds Fumadocs coverage for the Usage feature:
docs-fumadocs/content/docs/monitoring/usage.mdx— overview, metrics, filters, drill-down, data freshness/history, pricing overrides, and ops notesmonitoring/meta.json)intro.mdx(Core capabilities + Key guides)reference/cli-commands.mdx(seed-rates,diff-rates,recompute,sync-litellm, env tuning)feature-contributors.jsonand search indexNo application code changes in this commit.
Why?
The Usage feature was implemented in the app but had no user-facing documentation in Fumadocs. This fills that gap so reviewers and customers can understand how Usage works (metrics, drill-down, entitlements, pricing overrides, and ops) in the same style as other docs (Metrics, Calls, etc.).
How to Test?
Then locally:
http://localhost:3000/docs/monitoring/usage//docs/intro/and confirm the Usage link under Key guides/docs/reference/cli-commands/and confirm the Usage pricing sectionRelease Label
major- breaking change, next release bumps major versionminor- backward-compatible feature, next release bumps minor versionfix- backward-compatible bug fix, next release bumps patch versionIf you do not have permission to apply labels, mention the intended release label here and a maintainer will set it.
Checklist
CONTRIBUTING.mdguide.