Histogram of end-to-end request latency in seconds.
MetricPrometheusvLLM v0.23.0verified 11 hr ago
Identity
- Prometheus type
- histogram
- Labels
- model_nameengine
- Buckets
- 21 boundaries · 0.3 → 7680
- 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:e2e_request_latency_seconds observes one finished-request duration in seconds from arrival to logging-time completion. | Measurement semantics | 11 hr ago |
In vLLM v0.23.0, vllm:e2e_request_latency_seconds is computed when a request enters finished-request accounting using current time minus arrival_time. | Causal/runtime semantics | 11 hr ago |
In vLLM v0.23.0, vllm:e2e_request_latency_seconds combines queue, prefill, decode, and other request-lifecycle time rather than isolating one phase. | Interpretation & composition | 11 hr ago |
In vLLM v0.23.0, vllm:e2e_request_latency_seconds use phase histograms as companions before assigning cause; compare like request populations and workload distributions. | Guarded guidance | 11 hr ago |
In vLLM v0.23.0, vllm:e2e_request_latency_seconds is registered as a Prometheus histogram. | Structural identity | 11 hr ago |
In vLLM v0.23.0, vllm:e2e_request_latency_seconds is registered with the label names model_name, engine. | Structural identity | 11 hr ago |
In vLLM v0.23.0, vllm:e2e_request_latency_seconds declares 21 literal histogram bucket boundaries in its registration, from 0.3 to 7680.0. | Structural identity | 11 hr ago |
Availability
vllm:e2e_request_latency_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:870-878
Schema.ai