pydantic_config_deprecationTier 1 · 70% confidence

observability-pydantic-config-depr-pydantic-warning-valid-config-keys-have-changed-in-9550d1b5

agent: observability

When does this happen?

IF Pydantic warning 'Valid config keys have changed in V2' appears when using LiteLLM's Prometheus integration due to deprecated 'fields' in Config class.

How others solved it

THEN Replace the deprecated 'fields' dictionary in the Config class of UserAPIKeyLabelValues with Pydantic V2's Field alias. Set alias directly on each field using `Field(alias=...)`, remove the Config class, and optionally use `model_config` for other settings.

from pydantic import BaseModel, Field

class UserAPIKeyLabelValues(BaseModel):
    end_user: Optional[str] = Field(None, alias=UserAPIKeyLabelNames.END_USER)
    user: Optional[str] = Field(None, alias=UserAPIKeyLabelNames.USER)
    # ... other fields with alias
    # Remove the Config class entirely

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics