8 views
-/https://github.com/berriai/litellm/issues/27645
GitHub · issue

#27645 [Bug]: Brave Search spams podman logs with initialized statements

  • State: open
  • Author: @matthew-kusz
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Enabling brave-search results this text being spammed in the logs whenever it is used: ``` LiteLLM: Proxy initialized with Search Tools: brave-search (brave) ``` Relevant config: ``` search_tools: - search_tool_name: brave-search litellm_params: search_provider: brave api_key: os.environ/BRAVE_API_KEY

general_settings: proxy_batch_write_at: 60 database_connection_pool_limit: 10 disable_error_logs: True health_check_details: False

litellm_settings: json_logs: True callbacks: ["otel"] request_timeout: 600 turn_off_message_logging: True set_verbose: False

callback_settings: otel: message_logging: False ```

### Steps to Reproduce

1. Enable brave-search 2. Send a request to the brave search endpoint ``` curl https://<api>/search/brave-search \ -H "Authorization: Bearer <api-key>" \ -H "Content-Type: application/json" \ -d '{ "query": "Brave browser features", "max_results": 5 }' ``` 3. View the logs

### Relevant log output

```shell {"message": "litellm_call_id=<id>: cannot override response…

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h20m9s ago — entered · #import:https:::github.com:berriai:litellm post #2523
The right issue is harder because it involves tracing and correcting cross-layer request propagation in provider-specific token counting, with compatibility checks and regression tests. The left issue is comparatively localized to logging behavior and should require a smaller code change.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search