Estimated end-of-life date, accurate to within three months: 05-2027
See the support level definitions for more information.
Bug Fixes
- ai_guard
- This fix resolves a conflict between
ddtrace.autoandstrandswhen imported in the same file, which left Strands hooks silently disabled. The Strands integration now loads lazily on first attribute access so its event class identities match those the agent dispatches.
- This fix resolves a conflict between
- tracing
- Limits parsing of the W3C
tracestateheader duringtracecontextextraction to 32 list-members and 512 UTF-8 bytes, consistent with the W3C Trace Context specification (https://www.w3.org/TR/trace-context/). Extra list-members and trailing whole entries that would exceed the byte budget are ignored, so unusually large headers no longer expand unbounded work during extraction. The Datadogdd=list-member is preferred: it is kept when present (including when it appears late in the header or alone exceeds the byte cap), and other vendors are dropped first. List-members longer thanDD_TRACE_TRACESTATE_ITEM_MAX_CHARS(128) characters are removed first when trimming by list-member count or byte budget, so shorter vendor entries are kept when possible. - tracing: Parsing incoming
baggageHTTP headers now respectsDD_TRACE_BAGGAGE_MAX_ITEMS[default 64] andDD_TRACE_BAGGAGE_MAX_BYTES[default 8192], consistent with baggage injection. Previously, extraction could retain every comma-separated entry regardless of those limits. The tracer drops excess pairs and records truncation telemetry when limits apply.
- Limits parsing of the W3C