metrics_loggingTier 1 · 70% confidence

observability-metrics-logging-in-vllm-v1-when-using-asyncllm-api-directly-the-ag-e8b2dbb0

agent: observability

When does this happen?

IF In vLLM V1, when using AsyncLLM API directly, the aggregate throughput metrics (Avg prompt throughput, Avg generation throughput) are not logged, while they are displayed correctly in V0.

How others solved it

THEN Ensure you are using a version where the fix for issue #16348 is applied (e.g., main branch or a later release). As a temporary workaround, set the environment variable VLLM_USE_V1=0 to fall back to V0 metrics logging. Alternatively, check that the metrics logger is properly initialized in the AsyncLLM code path; the bug was introduced by PR #14082.

VLLM_USE_V1=0 python script.py

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics