vLLM v0.23.0 metric identity
broadvLLM v0.23.0evidence: source code
Coverage
Identity facts for the complete v0.23.0 Prometheus metric inventory — which metrics exist, their instrument kind, their label names, and their literal histogram bucket boundaries — generated from the pinned metric registration code.
Claims in this topic (94)
Metrics in this topic (45)
- cache_config_info
- corrupted_requests
- e2e_request_latency_seconds
- engine_sleep_state
- estimated_flops_per_gpu_total
- estimated_read_bytes_per_gpu_total
- estimated_write_bytes_per_gpu_total
- external_prefix_cache_hits
- external_prefix_cache_queries
- generation_tokens
- inter_token_latency_seconds
- iteration_tokens_total
- kv_block_idle_before_evict_seconds
- kv_block_lifetime_seconds
- kv_block_reuse_gap_seconds
- kv_cache_usage_perc
- lora_requests_info
- mm_cache_hits
- mm_cache_queries
- num_preemptions
- num_requests_running
- num_requests_waiting
- num_requests_waiting_by_reason
- prefix_cache_hits
- prefix_cache_queries
- prompt_tokens
- prompt_tokens_by_source
- prompt_tokens_cached
- request_decode_time_seconds
- request_generation_tokens
- request_inference_time_seconds
- request_max_num_generation_tokens
- request_params_max_tokens
- request_params_n
- request_prefill_kv_computed_tokens
- request_prefill_time_seconds
- request_prompt_tokens
- request_queue_time_seconds
- request_success
- request_time_per_output_token_seconds
- spec_decode_num_accepted_tokens
- spec_decode_num_accepted_tokens_per_pos
- spec_decode_num_draft_tokens
- spec_decode_num_drafts
- time_to_first_token_seconds
Surfaces
Known gaps
The corpus records no unit of measure for any v0.23.0 metric. vLLM's registration code has no structured unit field — `unit=` appears zero times in the pinned snapshots — so the only in-code signal is prose inside the `documentation=` argument, which states a unit for a minority of metrics and would require inference for the rest.
Five histogram metrics declare bucket boundaries computed at runtime via `build_1_2_5_buckets(max_model_len)` rather than as literal values; the corpus records no boundaries for them. Thirteen of the eighteen bucket declarations are literal and are recorded.
Nine metrics build their label set at runtime rather than declaring it statically — from a constructor parameter, from `metrics_info.keys()`, or from instance attributes — so the corpus records no label names for them. Thirty-six of the forty-five have statically resolvable label sets.