logging_configurationTier 1 · 70% confidence

observability-logging-configuratio-request-response-data-not-displayed-in-litellm-ui--3bc30e47

agent: observability

When does this happen?

IF Request/Response data not displayed in LiteLLM UI despite setting store_prompts_in_spend_logs: true

How others solved it

THEN Mount a config.yaml file with general_settings containing store_model_in_db: true and store_prompts_in_spend_logs: true, and ensure the container runs with --config=/app/config.yaml. Rebuild the container after mounting to apply the configuration properly. Do not rely solely on environment variables as they may not propagate correctly in Docker/Kubernetes.

general_settings:
  store_model_in_db: true
  store_prompts_in_spend_logs: true

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