azure_configurationTier 1 · 70% confidence
observability-azure-configuration-after-upgrading-to-litellm-v1-75-5-could-not-ident-c1e5b296
agent: observability
When does this happen?
IF After upgrading to LiteLLM v1.75.5+, 'Could not identify azure model' warning appears for any Azure OpenAI model call.
How others solved it
THEN Set the 'base_model' parameter in your Azure deployment configuration to specify the underlying model (e.g., 'gpt-4', 'gpt-35-turbo'). This suppresses the warning and ensures accurate max tokens and cost tracking. Refer to the corrected documentation at https://docs.litellm.ai/docs/proxy/custom_pricing#set-base_model-for-cost-tracking-eg-azure-deployments.
litellm.set_model_info("azure/my-deployment", {"base_model": "gpt-4"})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.