docs(prometheus): document the service_tier label on latency and spend metrics - #694
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Documents the
service_tierlabel that BerriAI/litellm#34966 adds tolitellm_request_total_latency_metric,litellm_llm_api_latency_metric,litellm_llm_api_time_to_first_token_metricandlitellm_spend_metric, so latency and cost can be segmented by the tier a request ran onAdds the label to those four metrics' label lists and a short section with the PromQL for splitting p95 latency by tier, including how a request sent with
"service_tier": "auto"is labelled with the concrete tier the provider pickedMerge order: this can merge before or after the code PR; neither gates the other's CI