Issue Station
Sign In
Tools hereToolbox

litellm - ✅(Solved) Fix [Bug]: Provider List: https://docs.litellm.ai/docs/providers [1 pull requests, 3 comments, 4 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
BerriAI/litellm#23879•Fetched 2026-04-08 00:54:04
View on GitHub
Comments
3
Participants
4
Timeline
14
Reactions
2
Author
RishangRishang
Participants
ArthurRenaultArthurRenaultKylinMountainKylinMountainoocxoocxRishangRishang
Timeline (top)
commented ×3labeled ×3subscribed ×3cross-referenced ×2

Fix Action

Fixed

PR fix notes

PR #23987: fix: remove noisy Provider List log message causing log flooding

Description (problem / solution / changelog)

Problem

The print statement for 'Provider List: https://docs.litellm.ai/docs/providers' was being triggered repeatedly when using non-OpenAI models (like OpenRouter), causing log flooding as reported in #23879.

Solution

Remove the redundant print statement. The error message already contains the documentation link ('Learn more: https://docs.litellm.ai/docs/providers'), so the separate print statement is unnecessary.

Changes

Fixes #23879

Changed files

  • litellm/litellm_core_utils/get_llm_provider_logic.py (modified, +0/-6)

Code Example

rovider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

Please remove this line it getting flooded in logs

Steps to Reproduce

  1. Use and non openai openrouter model in litellm

Relevant log output

rovider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/docs/providers


Provider List: https://docs.litellm.ai/

What part of LiteLLM is this about?

SDK (litellm Python package)

What LiteLLM version are you on ?

v1.82.3

Twitter / LinkedIn details

No response

extent analysis

Fix Plan

To prevent the "Provider List" log from flooding, we need to modify the logging configuration in the LiteLLM Python package.

Here are the steps:

  • Check the logging level: Ensure that the logging level is set to an appropriate level (e.g., INFO, WARNING, ERROR) to reduce the number of logs.
  • Modify the logger: Update the logger to ignore or reduce the frequency of "Provider List" logs.

Example code snippet:

import logging

# Set the logging level to INFO
logging.basicConfig(level=logging.INFO)

# Create a logger
logger = logging.getLogger(__name__)

# Ignore "Provider List" logs
def filter_provider_list_logs(record):
    if "Provider List" in record.getMessage():
        return False
    return True

# Add the filter to the logger
logger.addFilter(filter_provider_list_logs)

Alternatively, you can also use a logging configuration file to achieve this.

Verification

To verify that the fix worked, run your application and check the logs. The "Provider List" logs should be significantly reduced or eliminated.

Extra Tips

  • Make sure to test your application thoroughly after modifying the logging configuration to ensure that it works as expected.
  • Consider using a logging framework like Loguru or structlog for more advanced logging features.
  • If you're using a cloud logging service, check their documentation for configuration options to filter or ignore specific logs.

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…
#api#ssr#installation#tensor shape#autograd error#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING