log_spam_mitigationTier 1 · 70% confidence
observability-log-spam-mitigation-setting-disable-spend-updates-true-in-litellm-prox-3f48e55f
agent: observability
When does this happen?
IF Setting disable_spend_updates=True in LiteLLM proxy causes cost tracking callback to raise 'User API key and team id and user id missing' exception on every request, cluttering logs.
How others solved it
THEN Update the `_should_track_cost_callback` logic to return False when `disable_spend_updates` is enabled, or wrap the cost tracking callback to skip execution entirely when spend updates are disabled. This prevents the spurious exception and reduces log noise.
In your proxy configuration set `litellm.disable_spend_updates = True`. Then in `proxy_track_cost_callback.py`, modify `_should_track_cost_callback` to check the global setting: `if litellm.disable_spend_updates: return False`.
Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-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.