fix(proxy): set verbose_logger level when LITELLM_LOG=INFO

[he-yufeng]

Fixes #26396.

The `LITELLM_LOG=INFO` branch in `litellm/proxy/proxy_server.py` only set `verbose_router_logger` and `verbose_proxy_logger`. The third logger `verbose_logger` (used by e.g. `token_based_routing.py` via `litellm._logging.verbose_logger.info(...)`) inherited the Python root default (WARNING), so its INFO-level messages were silently filtered.

That's inconsistent with:

• The neighbouring `LITELLM_LOG=DEBUG` branch, which configures all three loggers.
• The `debug=True` / `detailed_debug=True` branches earlier in the same block, which also configure all three.

Include `verbose_logger` in the INFO branch so all three loggers behave the same.

Test plan

• `LITELLM_LOG=INFO litellm --config ...` now emits `verbose_logger.info(...)` messages (previously suppressed).
• No change to other log levels or branches.
• `uv run black .` clean on the touched file.

[veria-ai]

Low: Logging level fix only

This PR adds verbose_logger.setLevel(logging.INFO) to match the existing pattern for verbose_router_logger and verbose_proxy_logger when LITELLM_LOG=INFO. The same logger is already set in the DEBUG branch. No security impact.

---

Status: 0 open
Risk: 1/10

Posted by Veria AI · 2026-04-24T08:50:23.266Z

[greptile-apps]

Greptile Summary

This PR fixes a missing verbose_logger.setLevel(logging.INFO) call in the LITELLM_LOG=INFO branch of proxy_server.py. The omission caused INFO-level messages from verbose_logger (e.g. in token_based_routing.py) to be silently dropped while the other two loggers were correctly configured. The single-line addition now makes the INFO branch consistent with the DEBUG branch, the debug=True branch, and the detailed_debug=True branch.

Confidence Score: 5/5

This PR is safe to merge — it's a one-line additive fix with no risk of regression.

The change adds a single setLevel call that was clearly missing compared to every other sibling branch. No logic is altered, no interfaces change, and the fix is strictly additive.

No files require special attention.

Important Files Changed

Filename	Overview
litellm/proxy/proxy_server.py	Adds verbose_logger.setLevel(logging.INFO) and the corresponding import to the LITELLM_LOG=INFO branch, matching every other log-level branch in the same function.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[initialize called] --> B{debug is True?}
    B -- Yes --> C[Set all 3 loggers to INFO]
    B -- No --> D{detailed_debug is True?}
    D -- Yes --> E[Set all 3 loggers to DEBUG]
    D -- No --> F{LITELLM_LOG env var set?}
    F -- INFO --> G["Set verbose_logger ✅ NEW\nSet verbose_router_logger\nSet verbose_proxy_logger\n→ all INFO"]
    F -- DEBUG --> H["Set verbose_logger\nSet verbose_router_logger\nSet verbose_proxy_logger\n→ all DEBUG"]
    F -- other/unset --> I[No logger change]

Loading

_{Reviews (1): Last reviewed commit: "fix(proxy): set verbose_logger level whe..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing he-yufeng:fix/litellm-log-info-missing-verbose-logger (c26c446) with main (7b47dff)}

[codecov]

Codecov Report

❌ Patch coverage is 83.56941% with 58 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...opic/experimental_pass_through/adapters/handler.py	42.85%	12 Missing ⚠️
...y/management_endpoints/mcp_management_endpoints.py	80.95%	12 Missing ⚠️
litellm/proxy/auth/auth_checks.py	75.00%	7 Missing ⚠️
...rtex_ai/image_edit/vertex_imagen_transformation.py	58.33%	5 Missing ⚠️
.../llms/dashscope/image_generation/transformation.py	93.10%	4 Missing ⚠️
...llm/litellm_core_utils/prompt_templates/factory.py	25.00%	3 Missing ⚠️
...ass_through_endpoints/llm_passthrough_endpoints.py	62.50%	3 Missing ⚠️
...lms/black_forest_labs/image_edit/transformation.py	50.00%	2 Missing ⚠️
litellm/llms/vertex_ai/common_utils.py	71.42%	2 Missing ⚠️
...y/_experimental/mcp_server/semantic_tool_filter.py	94.11%	2 Missing ⚠️
... and 6 more

📢 Thoughts on this report? Let us know!