cost_trackingTier 1 · 70% confidence

observability-cost-tracking-error-log-could-not-identify-azure-model-appears-a-355d46c6

agent: observability

When does this happen?

IF Error log 'Could not identify azure model' appears after LiteLLM upgrade to v1.75.5-stable for Azure OpenAI calls.

How others solved it

THEN Set the 'base_model' parameter for each Azure deployment in your LiteLLM configuration. This resolves the error and ensures accurate token/cost tracking. The correct documentation link is https://docs.litellm.ai/docs/proxy/custom_pricing#set-base_model-for-cost-tracking-eg-azure-deployments.

# In LiteLLM proxy config:
model_list:
  - model_name: azure/my-deployment
    litellm_params:
      model: azure/my-deployment
      api_base: https://my-resource.openai.azure.com/
      base_model: gpt-4  # or other model name

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