Schema.aivllm:request_success
Counter for successfully processed requests, labeled by finished_reason.
MetricPrometheusvLLM v0.23.0verified 10 hr ago
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)
| Claim | Semantic layer | Verified |
|---|---|---|
In vLLM v0.23.0, vllm:request_success counts finished engine requests partitioned by finished_reason. | Measurement semantics | 10 hr ago |
In vLLM v0.23.0, vllm:request_success increments once for each FinishedRequestStats record consumed by the logger. | Causal/runtime semantics | 10 hr ago |
In vLLM v0.23.0, vllm:request_success is a completed-engine-request population and does not cover requests rejected before engine completion. | Interpretation & composition | 10 hr ago |
In vLLM v0.23.0, vllm:request_success sum only intended finish reasons for the question; use API or ingress telemetry for a denominator covering every HTTP attempt. | Guarded guidance | 10 hr ago |
In vLLM v0.23.0, vllm:request_success is registered as a Prometheus counter. | Structural identity | 10 hr ago |
In vLLM v0.23.0, vllm:request_success is registered with the label names model_name, engine, finished_reason. | Structural identity | 10 hr ago |
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