docs(prometheus): document PROMETHEUS_BUDGET_METRICS_PER_REQUEST_TIMEOUT env var#432
Open
fernando-izar wants to merge 1 commit into
Open
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 PROMETHEUS_BUDGET_METRICS_PER_REQUEST_TIMEOUT environment variable in the proxy config settings reference
This env var bounds how long per-request Prometheus budget metric emission may take before it is skipped, so a slow Redis/DB lookup cannot cancel the whole success-logging event. Default is 5.0 seconds
Pairs with the code change in BerriAI/litellm that adds the timeout. The litellm documentation CI (test_env_keys) requires every os.getenv key to be present in this reference table, so this entry unblocks that check