docs(proxy): document enterprise billable request metering - #571
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
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.
Summary
User-facing docs for the push-based billable-request metering shipped in BerriAI/litellm#31592. Adds docs/proxy/billing_metrics.md covering what the exported counter contains and deliberately excludes, which routes count as billable and how the count relates to the Admin UI successful-requests number, the five LITELLM_BILLING_METRICS_* environment variables with inline-PEM-or-path semantics, the positive enabled log line operators should verify on each metered component, and deployment recipes for the two Helm charts (billingMetrics block), the AWS/GCP Terraform reference stacks, and plain Docker. The page is registered under Setup & Deployment in sidebars.js, next to Multi-Region Deployment. The five environment variables are also added to the environment variables reference table in docs/proxy/config_settings.md, which the litellm repo's documentation CI checks against
Validated with npx docusaurus build; the new page builds and its links resolve (the pre-existing broken-link warnings on main are untouched)