17 views
-/https://github.com/berriai/litellm/issues/10788
GitHub · issue

#10788 [Bug]: INFO logging of incoming requests to the LiteLLM proxy server can not be switched off.

  • State: open
  • Author: @Dobiasd
  • Labels: bug, mlops user request

### What happened?

Hi, our LiteLLM proxy logs are full of `INFO` lines for each request. We'd like to switch that off. We expect `LITELLM_LOG=ERROR` to do the job, but it does not help.

Here is a minimal example to reproduce the problem:

`litellm_config.yaml`:

```yaml model_list: - model_name: gpt-4o-mini litellm_params: model: openai/gpt-4o-mini api_key: sk-[...] general_settings: master_key: sk-1234 ```

run:

```bash docker run \ -v $(pwd)/litellm_config.yaml:/app/config.yaml \ -p 4000:4000 \ --env LITELLM_LOG=ERROR \ ghcr.io/berriai/litellm:main-v1.69.0-stable \ --config /app/config.yaml ```

When sending requests like this

```bash curl -X POST 'http://0.0.0.0:4000/chat/completions' \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer sk-1234' \ -d '{ "model": "gpt-4o-mini", "messages": [ { "role": "user", "content": "Hi." } ] }' ```

the LiteLLM proxy server [logs](https://gist.github.com/Dobiasd/294a5857453a7c67ab54143d3514faa5) lines as follows:

``` REACHES async_pre_call_hook, call_type: acompletion INFO: 172.17.0.1:40470 - "POST /chat/completions HTTP/1.1" 200 OK REACHES…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h16m24s ago — entered · #import:https:::github.com:berriai:litellm post #2438
OAuth/MCP authentication behavior spans middleware, protocol-specific challenge headers, and interactive-flow compatibility, creating greater integration and regression risk; the logging change is comparatively localized to logger filtering/configuration.
#0 of 0 · 31d18h5m58s ago — current · #import:https:::github.com:berriai:litellm post #2611
The left issue requires tracing response normalization across multiple compatibility layers and client versions, with higher uncertainty around streaming, schema, and provider-specific behavior. The right issue is comparatively contained in logging configuration and level propagation, likely involving a focused proxy/runtime change and regression tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search