Release on: 2026-01-21
infrastructure_mode: end_user_device configuration option. When enabled, this mode automatically activates key monitoring features tailored for end-user devices including process collection, software inventory tracking, and notable events monitoring. These settings can still be individually overridden in the configuration file if needed.Add a new azure_metadata_api_version configuration option to allow customers to specify the Azure Instance Metadata Service (IMDS) API version used by the Agent. The default value is now 2021-02-01. This setting can be configured via azure_metadata_api_version in datadog.yaml or the DD_AZURE_METADATA_API_VERSION environment variable.
The Agent's embedded Python has been upgraded from 3.13.10 to 3.13.11
Fixed a potential race condition in the Cloud Foundry CCCache locking mechanism by replacing custom lock management with <span class="title-ref">singleflight</span>. This change improves handling of concurrent cache misses.
Add the canonical version annotation to the image named <span class="title-ref">internal.apm.datadoghq.com/[lang/injector]-canonical-version</span>. This makes it easier to track the actual version of the image used in the cluster, instead of just a digest or mutable tag.
Dogstatsd named pipe on Windows is now read/writeable for everyone by default. This prevents an Access is denied error when opening a named pipe for dogstatsd server on a Windows Azure App Service Web app. Security descriptor for the named pipe can be customized via dogstatsd_windows_pipe_security_descriptor.
Detect connection issue when using FQDN in agent diagnose
Agents are now built with Go 1.25.5.
The datadog-secret-backend now allows implicit Vault authentication to be set as a config option or an env var Added a configurable max_file_read_size config option to file.yaml, file.json, & file.text to prevent OOM reads
Added Microsoft Store apps to Windows Software Inventory integration.
Added a new boolean environment variable DD_OTELCOLLECTOR_GATEWAY_MODE for precise identification of the DDOT operating mode. The variable automatically configured via the Helm chart, the Operator, or set manually. Acceptable string values are (case insensitive): "true", "false", "1", "0"
The Discovery module is now enabled by default if system-probe is enabled. It can be disabled by setting discovery.enabled: false in system-probe.yaml, or by setting the DD_DISCOVERY_ENABLED environment variable to false.
The Agent's logger has been rewritten with a more modern library to improve security and performance. No visible change is expected for users. In case of issues, the previous logger can still be used by setting <span class="title-ref">log_use_slog</span> to <span class="title-ref">false</span> in the Agent configuration. This configuration will be removed in a future release.
Enable the orchestrator_explorer.kubelet_config_check.enabled by default.
Bump OpenTelemetry Collector dependencies to v0.141.0/v1.47.0
OTLP spans describing an HTTP error without an explicit error message will now fallback to one with a description, eg. "500 Internal Server Error" instead of just "500". Users who relied on the error message to extract the status code should use <span class="title-ref">http.response.status_code</span> instead.
Additionally, the error message is no longer sourced from the deprecated <span class="title-ref">http.status_text</span> attribute. This behavior can be overridden by explicitly setting the span's status message.
On Windows, adds process name to live processes via file properties.
Single Step Instrumentation now uses the Python tracer major version 4 by default. Customers instrumenting Python applications through SSI should review the [4.0.0](https://github.com/DataDog/dd-trace-py/releases/tag/v4.0.0) release notes and the [compatibility guide](https://docs.datadoghq.com/tracing/trace_collection/compatibility/python/) to ensure their Python applications are compatible.
Add flare support for workloadfilter component.
docker.cpu.shares metric values on cgroups v2 systems running runc >= 1.3.2 or crun >= 1.23. The new container runtimes use a different formula to convert CPU shares to cgroup v2 weight, which caused the Agent to report wrong values (e.g., 2597 instead of 1024 for default shares). The Agent now auto-detects which conversion formula the runtime uses and applies the correct inverse transformation.aws-us-gov) and China (aws-cn) regions. Previously, only the standard aws partition was accepted, causing ECS metadata extraction to fail for customers running the Datadog Agent in GovCloud or China regions. This resulted in empty region and account ID values, breaking ECS monitoring for these customers.ntp.offset metric using the timestamp returned by the NTP server rather than the local system clock. This restores the behavior present in Agent v5 and prevents incorrect metric alignment when host clocks are skewed.This feature is currently in development and is protected under the feature flag:
<span class="title-ref">cluster_checks.crd_collection</span>
For up-to-date docs, check out the secret-backend changelog, and the Datadog Secrets Management documentation
Refactored Cloud Foundry CCCache and BBSCache to use dependency injection to improve tests reliability and maintainability.
Released on: 2026-01-21 Pinned to datadog-agent v7.75.0: CHANGELOG.
The Datadog Cluster Agent's mutating webhooks (part of the [Admission Controller](https://docs.datadoghq.com/containers/cluster_agent/admission_controller/?tab=datadogoperator)) previously included Single Step Instrumentation (SSI) settings in their default webhook label selectors. These SSI-specific settings, <span class="title-ref">apm_config.instrumentation.enabled</span> and <span class="title-ref">apm_config.instrumentation.enabled_namespaces</span>, have been removed.
For those using Single Step Instrumentation, no action is required and no behavior changes. For those using the <span class="title-ref">config</span> or <span class="title-ref">tagsfromlabels</span> webhooks for manually instrumented applications, behavior remains consistent with the [documented configuration](https://docs.datadoghq.com/containers/cluster_agent/admission_controller/?tab=datadogoperator#apm-and-dogstatsd). Users that were unintentionally relying on the SSI settings without using SSI should add the appropriate pod label or enable <span class="title-ref">mutate_unlabelled</span> to preserve the previous behavior.
Fetched April 3, 2026