logging_controlTier 1 · 70% confidence

observability-logging-control-litellm-continues-to-emit-info-level-cost-calculat-ef51487c

agent: observability

When does this happen?

IF LiteLLM continues to emit INFO-level cost calculation logs even after setting LITELLM_LOG to WARNING and disabling debug and spend tracking.

How others solved it

THEN Set LITELLM_LOG environment variable before importing litellm. If logs persist, apply a custom logging filter to suppress messages containing 'selected model name for cost calculation' or 'Wrapper: Completed Call'. Upgrade to a fixed version once the patch is released.

import logging
class CostLogFilter(logging.Filter):
    def filter(self, record):
        return "cost calculation" not in record.getMessage() and "HTTP Request" not in record.getMessage()
logging.getLogger().addFilter(CostLogFilter())

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