vllm - 💡(How to fix) Fix [Usage]: Missing vllm:num_requests_running and other metrics in vLLM v0.18 when deploying Qwen3.5 27B [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#40605Fetched 2026-04-23 07:24:00
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1

Code Example

The output of `python collect_env.py`
RAW_BUFFERClick to expand / collapse

Your current environment

The output of `python collect_env.py`

How would you like to use vllm

I am using vLLM v0.18 to deploy the Qwen3.5 27B model. When accessing performance metrics via the /metrics endpoint, I noticed that some expected metrics, such as vllm:num_requests_running, are missing. What could be the reason for this?

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

extent analysis

TL;DR

The missing metrics in the /metrics endpoint may be due to a configuration or version issue with vLLM v0.18.

Guidance

  • Verify that the vllm:num_requests_running metric is supported in vLLM v0.18 by checking the documentation or release notes.
  • Check the configuration of the Qwen3.5 27B model deployment to ensure that metrics collection is enabled.
  • Review the output of python collect_env.py to identify any potential environment or configuration issues that may be contributing to the missing metrics.
  • Consider checking the vLLM documentation or community resources for known issues or workarounds related to metrics collection in v0.18.

Notes

The solution may depend on the specific configuration and deployment details of the Qwen3.5 27B model, which are not provided in the issue.

Recommendation

Apply workaround: Check the vLLM documentation and community resources for known issues or workarounds related to metrics collection in v0.18, as upgrading to a fixed version is not explicitly implied in the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix [Usage]: Missing vllm:num_requests_running and other metrics in vLLM v0.18 when deploying Qwen3.5 27B [1 participants]