Schema.ai· vLLM
vLLM official site Log in
All versions · Version range: v0.23.0

vllm:request_success

Counter for successfully processed requests, labeled by finished_reason.

MetricPrometheusverified Sep 29

Version history

  • The only version documented here is vLLM v0.23.0, where vllm:request_success is registered as a Prometheus counter with the label names model_name, engine, and finished_reason under the PrometheusStatLogger V1 metrics publisher.
  • In that same v0.23.0 snapshot, the counter measures finished engine requests partitioned by finished_reason, incrementing once per FinishedRequestStats record consumed by the logger.
  • Interpreting v0.23.0 data, the metric represents a completed-engine-request population that excludes requests rejected before engine completion, so you should sum only the finish reasons relevant to your question and rely on API or ingress telemetry for a denominator covering every HTTP attempt.

Identity

Prometheus type
counter
Labels
model_nameenginefinished_reason
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 (6)

Related Use Cases (2)

Availability

vllm:request_success is registered as a Prometheus counter 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:671-683