Schema.ai· vLLM· Schema 0.2.1
vLLM official site vLLM v0.23.0Log in

vllm:request_queue_time_seconds

Histogram of time spent in the WAITING phase per request.

MetricPrometheusvLLM v0.23.0verified 10 hr ago

Identity

Prometheus type
histogram
Labels
model_nameengine
Buckets
21 boundaries · 0.37680
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 (9)

ClaimSemantic layerVerified
In vLLM v0.23.0, vllm:request_queue_time_seconds observes one finished-request duration from queued_ts to the first scheduled_ts.Measurement semantics10 hr ago
In vLLM v0.23.0, vllm:request_queue_time_seconds is emitted on completion from scheduler lifecycle timestamps; repeated QUEUED events overwrite queued_ts while first SCHEDULED is retained.Causal/runtime semantics10 hr ago
In vLLM v0.23.0, vllm:request_queue_time_seconds measures the recorded waiting interval and includes only requests reaching finished-request accounting.Interpretation & composition10 hr ago
In vLLM v0.23.0, vllm:request_queue_time_seconds use quantiles with running/KV/token-progress metrics to distinguish admission delay from decode delay; no universal threshold is established.Guarded guidance10 hr ago
In vLLM v0.23.0, vllm:request_queue_time_seconds is registered as a Prometheus histogram.Structural identity10 hr ago
In vLLM v0.23.0, vllm:request_queue_time_seconds is registered with the label names model_name, engine.Structural identity10 hr ago
In vLLM v0.23.0, vllm:request_queue_time_seconds declares 21 literal histogram bucket boundaries in its registration, from 0.3 to 7680.0.Structural identity10 hr ago
For each EngineCoreEventType.QUEUED event processed by IterationStats.update_from_events, req_stats.queued_ts is set to event.timestamp.Interpretation & composition10 hr ago
In vLLM v0.23.0, queued_time is computed as req_stats.scheduled_ts - req_stats.queued_ts; the source comment describes the queued interval as from first QUEUED event to first SCHEDULED.Interpretation & composition10 hr ago

Related Use Cases (1)

Availability

vllm:request_queue_time_seconds is registered as a Prometheus histogram 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:880-888