Release on: 2025-12-10
Replace batch processor with exporter helper for OTLP ingest due to the upcoming end-of-life for batch processor. More details: https://github.com/open-telemetry/opentelemetry-collector/issues/8122
Remote Agent Management now creates a new directory that is at the same level as the current Agent configuration directory.
This directory is used during remote configuration updates and is deleted after the update is complete.
Added a new core check to send raw Kubelet configuration manifests to the Kubernetes Orchestrator.
Added comprehensive support for AWS ECS Managed Instances, including automatic deployment mode detection, hostname resolution for sidecar deployments, and validation logic to prevent misconfigured deployments.
Configure filtering for collection of autodiscovered metrics and logs through CEL-based rules using <span class="title-ref">cel_workload_exclude</span>.
Collect container metrics for ECS Managed Instances when running in sidecar mode.
APM: A more efficient trace payload encoding through the /v1.0/traces endpoint has been added.
Update JMXFetch to 0.51.0 to add configuration-level dynamic tags for JMX attribute values via dynamic_tags
Remote Agent Management is now enabled by default for Agents running on Linux and Windows hosts. This feature allows you to remotely upgrade and configure the Agent from the Datadog UI in Fleet Automation.
To disable, set remote_updates to false in the Agent configuration file.
The Datadog Installer now supports installing the datadog-apm-inject package on Windows systems.
Adds kubernetes_state.daemonset.rollout_duration metric to the KSM check.
Implement check filtering in the scheduler and CLI to enforce infrastructure basic mode restrictions. When running in basic mode (infrastructure_mode: "basic"), only core system checks (cpu, disk, memory, network, uptime, load, io, file_handle, ntp, system_core, telemetry) are allowed to execute. Additional checks can be allowlisted via the allowed_additional_integrations configuration option.
The Agent's embedded Python has been upgraded from 3.13.7 to 3.13.10
Network Path Collector (network traffic paths) now performs traceroutes using domain names instead of IP addresses.
This release refactors the ECS workloadmeta collector architecture to clearly separate ECS launch type (EC2 vs Fargate) from agent deployment mode (daemon vs sidecar). This improves code organization, reduces duplication, and helps future Managed Instances support.
KSM now supports using a wildcard to collect all resource labels/annotations as tags on metrics.
Added CCRID (Canonical Cloud Resource ID) support for Oracle Cloud Infrastructure hosts.
Add helpers for translating OTLP duration histograms to DDSketch in the <span class="title-ref">pkg/opentelemetry-mapping-go/otlp/metrics</span> package.
APM: The Trace Agent now omits infrequently used statistics when their values are zero, reducing overhead.
This can be overridden by setting the new configuration option <span class="title-ref">apm_config.send_all_internal_stats</span> to true.
Agents are now built with Go 1.24.9.
The Cluster Agent now enables both <span class="title-ref">DD_CLUSTER_CHECKS_ADVANCED_DISPATCHING_ENABLED</span> and <span class="title-ref">DD_CLUSTER_CHECKS_REBALANCE_WITH_UTILIZATION</span> by default. These options are now set to <span class="title-ref">true</span> in both the configuration template and the code, improving cluster check dispatching and balancing based on node utilization out-of-the-box. To disable these features, a user must now explicitly set them to <span class="title-ref">false</span> with the following config options: - name: DD_CLUSTER_CHECKS_ADVANCED_DISPATCHING_ENABLED value: "false" - name: DD_CLUSTER_CHECKS_REBALANCE_WITH_UTILIZATION value: "false"
Enable the Go disk and network core checks by default for Windows and Linux. These are direct ports of the existing Python disk and network checks and allow the Python runtime to be lazy loaded when other integrations are enabled. It can be disabled with setting use_diskv2_check and use_networkv2_check respectively along with the loader in your configuration to use the Python version.
Python runtime will now be lazy loaded when there are no Python integrations configured. This can be disabled by setting python_lazy_loading: false in your configuration.
Allow check configurations to be matched to services using CEL selectors in Autodiscovery. This allows for more granular targeting of configurations to services based on their metadata.
Adds the count of total GPU devices to the telemetry metrics emitted to Datadog.
GPU: emit count metrics for NVIDIA Xid errors
Adds DD_INFRASTRUCTURE_MODE install option to the datadog-installer-x86_64.exe installer and the Windows MSI installer. Set DD_INFRASTRUCTURE_MODE to configure the infrastructure_mode configuration option at installation.
The infraattributes processor can now be run when the Datadog Exporter is not configured.
Add <span class="title-ref">--enable</span> and <span class="title-ref">--disable</span> commands to the IIS .NET APM instrumentation management script on Windows
Windows: Adds a PURGE argument to the MSI to remove all OCI packages during uninstallation.
The Workload Protection's activity dump functionality on Linux has been improved to reduce its impact on processes that use very large amounts of memory.
Cache result of <span class="title-ref">TagsToString()</span> in serverless-init to improve CPU performance.
The DDOT service runs as ddagentuser.
Released on: 2025-12-10 Pinned to datadog-agent v7.73.0: CHANGELOG.
This change removes support for v1 of the auto-instrumentation webhook used for Single Step Instrumentation. The v2 implementation, which has been the default since Agent v7.57.0, is a drop-in replacement. This setting was never exposed in Helm or the Datadog Operator. If you previously set the DD_APM_INSTRUMENTATION_VERSION environment variable on the Cluster Agent, it is now ignored.
If you use a private registry, add the <span class="title-ref">apm-inject</span> container to your registry before upgrading. No action is required for other users. For details on using private registries, see Use a private container registry.
Customers using Single Step Instrumentation with target-based workload selection can now use language detection. Language detection greatly reduces startup time when all default libraries are configured for a target.
A target is eligible for language detection if a target has no defined <span class="title-ref">ddTraceVersions</span> or if <span class="title-ref">ddTraceVersions</span> matches the default set of SDKs. Once a language has been determined for a deployment, subsequent deploys only use the SDKs necessary for the detected language.
kube-system and the Datadog Agent's namespace) resources from Admission Controller mutation webhooks. This prevents mutation webhooks from unnecessarily intercepting system namespace resources, reducing misleading warnings or logs, and improving clarity about which resources are actually mutated.Fetched April 3, 2026