●Change8

Migrating to Datadog SDK v4.9.0

Version v4.9.0 introduces 1 breaking change. This guide details how to update your code.

Released: 5/26/2026

1
Breaking Changes
2
Migration Steps
7
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

ddtrace.appsec.ai_guard.AIGuardAbortErrorddtrace.internal._exceptions.DDBlockExceptionLLMObs.annotateLLMObs.annotation_contextDataDogProvidertracer.wrapOpenAI SDK chat completions instrumentation

Breaking Changes

●Issue #1

Azure CosmosDB spans no longer include the `http.status_code` tag; it has been replaced by the `db.response.status_code` metric. Users relying on `http.status_code` on `cosmosdb.query` spans from v4.8.0 must update their queries to use `db.response.status_code`.

Migration Steps

  1. 1
    If you were relying on the `http.status_code` tag on Azure CosmosDB spans, update your queries to use the `db.response.status_code` metric instead.
  2. 2
    Replace usage of the deprecated environment variable `DD_TRACE_INFERRED_SPANS_ENABLED` with `DD_TRACE_INFERRED_PROXY_SERVICES_ENABLED`.

Release Summary

This release introduces significant enhancements for LLM Observability, AI Guard integration, and CI Visibility, alongside fixing several critical bugs related to coverage and tracing instrumentation. A breaking change affects how HTTP status codes are reported for Azure CosmosDB spans.

Need More Details?

View the full release notes and all changes for Datadog SDK v4.9.0.

View Full Changelog