feat(prometheus): add queue depth metrics for deployments #17862
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
Add Prometheus gauge metrics to monitor active and queued requests per deployment when using
max_parallel_requestslimiting.TrackedSemaphorewrapper that tracks queue depth without accessing privateasyncio.Semaphoreinternalslitellm_deployment_active_requestsgauge metriclitellm_deployment_queued_requestsgauge metricRouter.get_deployment_queue_stats()methodProblem
LiteLLM Router uses semaphores for
max_parallel_requestslimiting but provides no visibility into queue depth. Operators cannot monitor:Solution
TrackedSemaphore
A wrapper around
asyncio.Semaphorethat explicitly tracksactiveandqueuedcounts:Prometheus Metrics
Test Plan
Performance
The overhead is negligible because LLM API calls take 100ms-10s while semaphore operations take microseconds.
Closes #17764