Driftwatch

Datadog / Datadog API v2 /

Breakingdirection flip: their tools call this safe

value can now return "amazon_bedrock", "azure_openai", "datadog", "datadog_ai_gateway", "deterministic", "insights_sponsored", "llmproxy", "typesafe", "vertex_ai"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects this value on LLMObsCustomEvalConfigIntegrationProvider reachable from 3 operations.

New values: amazon_bedrock, azure_openai, datadog, datadog_ai_gateway, deterministic, insights_sponsored, llmproxy, typesafe, vertex_ai.

can now return "amazon_bedrock", "azure_openai", "datadog", "datadog_ai_gateway", "deterministic", "insights_sponsored", "llmproxy", "typesafe", "vertex_ai"

Who is affected

Code that reads 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

switch (response) {
  // existing branches …
  // no branch for "amazon_bedrock"
  // no branch for "azure_openai"
  // no branch for "datadog"
  // no branch for "datadog_ai_gateway"
  // no branch for "deterministic"
  // no branch for "insights_sponsored"
  // no branch for "llmproxy"
  // no branch for "typesafe"
  // no branch for "vertex_ai"
  default:
    throw new Error("unexpected value");
}

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