Driftwatch

Datadog / Datadog API v2 /

Breaking

value no longer accepts "amazon-bedrock", "azure-openai", "llm-proxy", "vertex-ai"

What changed

A value you may have hardcoded is now rejected.

Affects LLMObsCustomEvalConfigIntegrationProvider reachable from 3 operations.

no longer accepts "amazon-bedrock", "azure-openai", "llm-proxy", "vertex-ai"

Who is affected

Code that sends Datadog's LLMObsCustomEvalConfigIntegrationProvider objects, used by 3 Datadog operations.

Before and after

WhereBeforeAfter
LLMObsCustomEvalConfigIntegrationProvider"amazon-bedrock", "anthropic", "azure-openai", "llm-proxy", "openai", "vertex-ai""amazon_bedrock", "anthropic", "azure_openai", "datadog", "datadog_ai_gateway", "deterministic", "insights_sponsored", "llmproxy", "openai", "typesafe", "vertex_ai"

Code that breaks

// sending "amazon-bedrock" for undefined is now rejected
// sending "azure-openai" for undefined is now rejected
// sending "llm-proxy" for undefined is now rejected
// sending "vertex-ai" for undefined is now rejected

Based on Datadog’s published API specification. How severity is decided.