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.
MetricvLLM v0.23.0confidence: highverified 10 hr agoverified-code
Metric
e2e_request_latency_secondsApplies when
PrometheusStatLoggerV1 metrics
Evidence
vLLM v0.23.0 v1 metrics stats.py(vllm/v1/metrics/loggers.py:430-475)
definesprimarysource_codecode_introspection
Does not establish
- a workload-independent healthy threshold
- semantics in any vLLM version other than v0.23.0
Guards
vllm_version= v0.23.0metric_name=vllm:e2e_request_latency_seconds