Gauge for the number of requests in model execution batches.
MetricPrometheusvLLM v0.23.0verified 10 hr ago
Identity
- Prometheus type
- gauge
- Labels
- model_nameengine
- Unit
- Not recorded — vLLM registration code has no structured unit field, and units are not inferred from name suffixes
Semantic coverage
covered · Availability & namecovered · Structural identitycovered · Measurement semanticscovered · Causal/runtime semanticscovered · Interpretation & compositioncovered · Guarded guidance
Metric knowledge (7)
| Claim | Semantic layer | Verified |
|---|
In vLLM v0.23.0, vllm:num_requests_running is a point-in-time gauge of requests currently running in model execution batches. | Measurement semantics | 10 hr ago |
In vLLM v0.23.0, vllm:num_requests_running is set from scheduler running-request state at a logging snapshot. | Causal/runtime semantics | 10 hr ago |
In vLLM v0.23.0, vllm:num_requests_running measures concurrency rather than arrivals, completions, successes, or failures. | Interpretation & composition | 10 hr ago |
In vLLM v0.23.0, vllm:num_requests_running use it with waiting, KV pressure, and token progress to describe load; never use it as an error-rate denominator. | Guarded guidance | 10 hr ago |
In vLLM v0.23.0, vllm:num_requests_running is registered with the label names model_name, engine. | Structural identity | 10 hr ago |
In vLLM v0.23.0, vllm:num_requests_running is a Prometheus gauge for the number of requests in model execution batches. | Structural identity | 10 hr ago |
In vLLM v0.23.0, vllm:num_requests_running is set from SchedulerStats.num_running_reqs and observes scheduler running-request state. | Interpretation & composition | 10 hr ago |
Availability
vllm:num_requests_running is registered as a Prometheus gauge in vLLM v0.23.0.
vllm.surface.prometheus_metricscomplete_inventoryPrometheusStatLogger metrics publisher
vLLM v0.23.0 v1 metrics loggers.py · vllm/v1/metrics/loggers.py:451-459
Schema.ai