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 entirelyRelated 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.