log_level_ignoredTier 1 · 70% confidence

observability-log-level-ignored-when-litellm-log-warning-and-various-disable-flags-d8288eda

agent: observability

When does this happen?

IF When 'LITELLM_LOG=WARNING' and various disable flags are set, LiteLLM still prints INFO-level logs for cost calculation (e.g., 'selected model name for cost calculation') for every request, especially when importing litellm through another module.

How others solved it

THEN Fix the logging configuration to respect the 'LITELLM_LOG' environment variable globally and ensure cost calculation logs are suppressed when log level is set to WARNING or higher. Also verify that the logging override works when litellm is called from imported modules, not just the main script.

os.environ['LITELLM_LOG'] = 'WARNING'
litellm.set_verbose = False
litellm._logging._disable_debugging()

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