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.
Relevant issues
Addresses user request for enhanced Prometheus metrics.
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-unitCI (LiteLLM team)
Branch creation CI run
Link:
CI run for the last commit
Link:
Merge / cherry-pick CI run
Links:
Type
🆕 New Feature
Changes
WHY: Users require the
model_idlabel in key Prometheus metrics to accurately calculate success rates and analyze performance at the specific model deployment level, enhancing observability beyond just therequested_model.WHAT:
model_idlabel to the following Prometheus metrics:litellm_proxy_total_requests_metriclitellm_proxy_failed_requests_metriclitellm_request_total_latency_metriclitellm_llm_api_time_to_first_token_metric(TTFT)litellm/integrations/prometheus.pyto utilizeprometheus_label_factoryfor consistent label handling.docs/my-website/docs/proxy/prometheus.md) to reflect the new labels.model_idin the affected metrics.Slack Thread