Release on: 2025-12-01
Released on: 2025-12-01 Pinned to datadog-agent v7.72.4: CHANGELOG.
Release on: 2025-11-26
Released on: 2025-11-26 Pinned to datadog-agent v7.72.3: CHANGELOG.
Release on: 2025-11-12
Install-Datadog.ps1 and datadog-installer-x86_64.exe) does not reinstall the Agent if the same version was just uninstalled.Released on: 2025-11-12 Pinned to datadog-agent v7.72.2: CHANGELOG.
Release on: 2025-11-06
Released on: 2025-11-06 Pinned to datadog-agent v7.72.1: CHANGELOG.
Release on: 2025-11-03
The Agent's embedded Python has been upgraded from 3.12.11 to 3.13.7
The PowerShell install script Install-Datadog.ps1 now executes a different datadog-installer-x86_64.exe subcommand.
If you always download a fresh Install-Datadog.ps1, then no changes are needed.
If you have a cached or modified copy of Install-Datadog.ps1, then you must merge the latest changes, or migrate to use the executable setup instead. See the features section for more information.
Install-Datadog.ps1 is now a light wrapper for downloading and executing datadog-installer-x86_64.exe. The rest of the setup responsibility has been moved into the executable.
The Agent now emits the <span class="title-ref">kube_distribution</span> tag based on labels in managed Kubernetes installations with values: eks, gke and aks.
Add the new metric <span class="title-ref">kubernetes.pod.resize.pending</span> to kubelet check to track pods that have pending resource resize request that can't be satisfied right now. Metrics has <span class="title-ref">reason</span> tag.
Print service details in the Agent configcheck verbose command output.
Add Windows DDOT OCI package to support Datadog OpenTelemetry
The trace-agent running in the Azure App Services Extension now adds function tags to the tracer payloads that it sends to Datadog. This allows the traces to be queried by the trace tags, which is particularly useful for standard filtering in the Datadog UI.
Add support of CIS Red Hat Enterprise Linux 10 Benchmark in CSPM.
Add support of CIS Ubuntu 24.04 Benchmark in CSPM.
Added Datadog OTEL agent as Windows service
This is part of the effort to add Datadog OpenTelemetry agent as a Windows service.
Adds support for UDP, ICMP, and TCP Network Path for Windows Client OSes using ddnpm driver.
Added new Windows Server 2025 container images:
Release tags:
agent:7-ltsc2025 and agent:latest-ltsc2025agent:7-servercore-ltsc2025 and agent:latest-servercore-ltsc2025agent:7-ltsc2025-jmx and agent:latest-ltsc2025-jmxagent:7-servercore-ltsc2025-jmx and agent:latest-servercore-ltsc2025-jmxRelease candidate tags:
agent:7-rc-ltsc2025agent:7-rc-servercore-ltsc2025agent:7-rc-ltsc2025-jmxagent:7-rc-servercore-ltsc2025-jmxVersion-specific release candidate tags (such as agent:7.X.Y-rc.Z-ltsc2025, agent:7.X.Y-rc.Z-servercore-ltsc2025) are also supported.
Updated the base multi-arch images to include Windows 2025 images alongside existing Windows 2019 and Windows 2022 variants.
The Agent can now be configured to restrict which secrets from Kubernetes can be by integration (only apply to secret using the <span class="title-ref">k8s_secret@</span> prefix).
Three new settings have been introduced, allowing different levels of control (see datadog.yaml.example for more information).
Added integration test to ensure correct population of service and source tags on the truncate log metric.
USM HTTP2 monitoring configuration now uses a tree structure for improved organization and consistency with other protocol configurations.
Configuration changes:
The previous configuration paths are deprecated but still supported for backward compatibility. Users will receive deprecation warnings and should migrate to the new tree structure. If both old and new configurations are present, the new tree structure takes precedence.
Environment variable changes:
The datadog-installer-x86_64.exe executable can now be used in place of the Install-Datadog.ps1 PowerShell script. The executable is versioned and will only install that version. For example, to install Agent 7.72.0, download and run https://install.datadoghq.com/datadog-installer-7.72.0-1-x86_64.exe. For more information, refer to the [in-app install instructions](https://app.datadoghq.com/fleet/install-agent/latest?platform=windows).
To install the latest stable Agent version, download and run https://install.datadoghq.com/datadog-installer-x86_64.exe. This executable file is also versioned and will only install one version. It is updated with each release.
To check the version, run .\datadog-installer-x86_64.exe version.
Add resize policies for CPU and memory as tags for containers when they are explicitly set on workloads.
Fix config path patterns for Python 3.13 and add SpecifierSet error handling.
The cluster agent API now supports querying for node UIDs by name.
Add support for KSM custom resource definition metrics of type Info, enabling collection and forwarding of custom resource info metrics
Added tracking of check worker utilization. Utilization stats can be seen using the <span class="title-ref">agent status</span> command. In addition, the Datadog Agent will log a warning if a worker's utilization exceeds a threshold (95% by default).
Add support for upstream datadogextension to DDOT.
Adds kubernetes.statefulset.rollout_duration metric to ksm check.
Added a new 'process' type to the workload filtering system for future use cases.
Add --json and --pretty-json flags to the health command that will output the health status as JSON.
[APM] Add support for sql_obfuscation_mode=normalize_only. This mode configures the SQL obfuscator to only normalize the values, without obfuscating them.
Agents are now built with Go 1.24.9.
Windows: Cache event publisher metadata to avoid repeated expensive calls to EvtOpenPublisherMetadata.
The <span class="title-ref">gcp.run.job.enhanced.task.ended</span> enhanced shutdown metric for Cloud Run Jobs now includes the exit code as a tag.
Since version 7.67.0, the site is converted to a FQDN if it is one of Datadog's domains. A configuration option convert_dd_site_fqdn.enabled has been added to allow disabling this behavior.
Add support for oss datadog extension in converter.
Create TCP endpoints for multi-region failover.
Support for custom queries based scaling in Datadog Pod Autoscaler
The agent config command now displays only user-configured settings by default, excluding default values. Use agent config --all to display all settings including defaults (previous behavior).
Added exponential backoff to host metadata collection at startup to increase early host-payload frequency and speed up node-level tag availability.
Enhanced fingerprinting configuration with file-specific overrides and improved fallback behavior. <span class="title-ref">logs_config.fingerprint_config</span> can now be set on a per-source and global basis, as either [disabled, line_checksum, byte_checksum].
File-specific configurations take precedence over global settings, with automatic fallback to global config when file configs are missing or incomplete.
The Datadog Installer now keeps YAML comments when updating the Agent configuration during installation. While comment text is preserved, its format may not be. Changes to whitespace, indentation, or blank lines may occur.
Migrates the WorkloadMeta filtering system to use the new filtering component. This ensures a consistent experience across all resources.
Allows NetPath on Windows without local firewall changes.
Network Path will now run multiple traceroutes and end-to-end probes for each endpoint.
Set the 'provider-kind' tag at the beginning of the static tag list.
For better troubleshooting, secret backend version information is now included in the <span class="title-ref">agent secret</span> command, flare output, and other metadata when <span class="title-ref">secret_backend_type</span> is configured and the backend executable supports the <span class="title-ref">--version</span> flag.
Avoid ReadString allocation in serverless-init log processing for improved efficiency.
Use <span class="title-ref">zstd</span> compression on logs in serverless-init for better performance.
dbm: add SQL obfuscation <span class="title-ref">ReplaceBindParameter</span> option to support obfuscating SQL bind parameters.
Update database monitoring payloads to use the default compression kind.
Enhanced Windows BSOD reports to include bugcheck arguments. Updated internal filter that drops irrelevant BSOD reports to look for a Datadog driver in any frames of the callstack instead of only the first frame.
Enhance Windows BSOD reports to include the crash call stack and the Agent version found in the crash dump.
--python argument is no longer used in the integrations subcommand.service_monitoring_config.enable_http_monitoring, service_monitoring_config.max_http_stats_buffered, service_monitoring_config.max_tracked_http_connections, service_monitoring_config.http_notification_threshold, service_monitoring_config.http_max_request_fragment, service_monitoring_config.http_map_cleaner_interval_in_s, service_monitoring_config.http_idle_connection_ttl_in_s, and service_monitoring_config.http_replace_rules. Use the new tree structure under service_monitoring_config.http.* instead (e.g., service_monitoring_config.http.enabled, service_monitoring_config.http.max_stats_buffered). The deprecated keys remain fully backward compatible, but the new tree structure takes precedence when both are configured.agent status command.Added the following agent telemetry metrics for debugging gRPC communication within the agent:
| Metric Name | Type | Description |
|---|---|---|
| <span class="title-ref">grpc.request_count</span> | Counter | Total number of gRPC requests processed by the agent |
| <span class="title-ref">grpc.error_count</span> | Counter | Total number of gRPC errors encountered by the agent |
| <span class="title-ref">grpc.request_duration_seconds</span> | Histogram | Distribution of gRPC request latencies for agent communication |
| <span class="title-ref">grpc.payload_size_bytes</span> | Histogram | Distribution of payload sizes for gRPC calls within the agent |
Add new metric origins to the Agent for BentoML, Hugging Face TGI, and IBM Spectrum LSF.
CPU and wall clock time collection in Python profiling is temporarily disabled to maintain compatibility with Python 3.13.
Add new metrics to the Agent's origins for Datadog Operator.
Released on: 2025-11-03 Pinned to datadog-agent v7.72.0: CHANGELOG.
Release on: 2025-10-15
Released on: 2025-10-15 Pinned to datadog-agent v7.71.2: CHANGELOG.
Release on: 2025-10-08
Fixes configuration parsing for extended container metric collection on the container core check.
Fix Remote Agent management configuration changes on Windows.
Fix race condition that in rare cases caused remote updates on Windows to fail without an error.
The Go context used when creating a detached subprocess was closed on exit. This triggered an async action to kill the detached subprocess, which in rare cases completed before the process exited.
Released on: 2025-10-07 Pinned to datadog-agent v7.71.1: CHANGELOG.
Release on: 2025-10-01
Added eBPF support for the <span class="title-ref">prctl</span> syscall. The following fields are now collected:
The infraattributes processor included in DDOT pipelines can now determine a missing <span class="title-ref">container.id</span> attribute based on (in order of priority):
This PR adds the HTTP Method and HTTP Endpoint to the stats protobuf file for the resource renaming feature.
DogStatsD emits a new metric, metric_type_count, that tracks total gauges, counters, etc.
Remote tagger is now enabled by default in Datadog cluster check runners, resulting in improved tag support and coverage for metrics from checks such as <span class="title-ref">kube_state_core</span> when configured to run in cluster check runners.
Improved logs destination warning log with additional endpoint metadata such as full url, track type, EvP category, and origin.
Displays the partially redacted API key to each endpoint on the Logs Agent status page.
Add debugger v2 intake proxy.
Add scrubber to JMX integration config and metadata.
Add the new metric <span class="title-ref">kubernetes.pod.terminating.duration</span> to kubelet check to track pods that are stuck in the termination phase. If <span class="title-ref">deletionTimestamp</span> is set to a time in the future,`kubernetes.pod.terminating.duration` is only emitted when the current time reaches the time set in <span class="title-ref">deletionTimestamp</span>.
Adds kubernetes.deployment.rollout_duration metric to ksm check.
On Linux, the Agent is now able to bind to ports below 1024 by default, simplifying common logs, SNMP, and integrations configurations. This is done by setting <span class="title-ref">AmbientCapabilities=CAP_NET_BIND_SERVICE</span> in the Agent systemd units.
If you want to disable this, create a systemd drop-in file (e.g., <span class="title-ref">/etc/systemd/system/datadog-agent.service.d/disable-capability.conf</span>) with: ` [Service] AmbientCapabilities=`.
Added <span class="title-ref">kube_argo_rollout</span> tag for workloads controlled by Argo Rollouts.
Agents are now built with Go 1.24.6.
APM: Add new configuration "DD_APM_CLIENT_STATS_FLUSH_INTERVAL" to adjust client stats flushing interval. This can be used to test if longer flushing intervals can improve stats processing throughput.
Consistently retrieve the socket protocol (sk_protocol) and include it in the key for the flow PID map. This change ensures that the flow PID map uses a consistent key format that includes the socket protocol, improving the accuracy and reliability of flow tracking in network operations.
Increase the Logs Agent default max message payload size from 256 KB to 900 KB.
Install-Datadog.ps1 now checks that the downloaded datadog-installer-x86_64.exe has a valid Datadog code signature.
gather and expose kubernetes state metrics for init containers. gather and expose init containers resources requests and limits when container is set with <span class="title-ref">restartPolicy=Always</span>.
Add a new tag <span class="title-ref">kube_static_cpus</span> on kubernetes CPU metrics that indicates whether a container is using dedicated cores.
Adds a <span class="title-ref">disable</span> field to <span class="title-ref">interface_configs</span> to disable metric collection for selected interfaces.
Add RUM support to the OpenTelemetry mapping library.
DDOT now supports sending host metadata from OTel resource attributes. This is required for Gateway support. See https://docs.datadoghq.com/opentelemetry/mapping/host_metadata/ on how to configure the attributes.
The non-DDOT OTLP ingestion pipelines for traces and metrics now include the infraattributes processor, enabling more complete Kubernetes tag enrichment.
pkg/opentelemetry-mapping-go: Sync with upstream library through [commit 7c614b196a40f883502e86e195e89c233b4c1006](https://github.com/DataDog/opentelemetry-mapping-go/commit/7c614b196a40f883502e86e195e89c233b4c1006).
pkg/util/quantile: Sync with upstream library through [commit 7c614b196a40f883502e86e195e89c233b4c1006](https://github.com/DataDog/opentelemetry-mapping-go/commit/7c614b196a40f883502e86e195e89c233b4c1006).
Adds complete workloadmeta process-entity information to workload-list command logs (datadog-agent workload-list)
Install-Datadog.ps1 now displays error messages when run in environments without a proper console, such as PSRemoting or PowerShell ISE./norestart MSI option to prevent Windows from automatically rebooting the host in rare cases when files are in use.Add <span class="title-ref">checks.delay</span> and <span class="title-ref">checks.runs</span> telemetry metrics for the agent checks. This enables break down and analysis by <span class="title-ref">check_name</span> and <span class="title-ref">state</span> where applicable.
Add a metric counter to the Agent telemetry for hostname.drift_detected. This helps track whether hostname resolution issues occur during the Agent's lifetime.
Add a new telemetry for <span class="title-ref">inuse_bytes</span>, <span class="title-ref">frees</span>, and <span class="title-ref">allocations</span> to monitor rtloader memory usage and behavior.
Scrubber: Added support for additional sensitive keys in configuration scrubbing:
x-seel-api-key, x-goog-api-key, x-sonar-passcodex-consul-token, x-datadog-monitor-token, x-vault-token, x-vtex-api-apptoken, x-static-tokenx-api-secret, x-ibm-client-secret, x-chalk-client-secretcookie, private-token, kong-admin-token, accesstoken, session_tokenThese keys will now be automatically scrubbed from configuration files, logs, and other sensitive data to prevent accidental exposure of credentials.
Released on: 2025-10-01 Pinned to datadog-agent v7.71.0: CHANGELOG.
Added support for gradual rollout in K8s SSI deployments. This feature is enabled if the following conditions are met:
DD_ADMISSION_CONTROLLER_AUTO_INSTRUMENTATION_ENABLED=true and/or DD_APM_INSTRUMENTATION_ENABLED=true- Using a Datadog registry (gcr.io/datadoghq, hub.docker.com/r/datadog, gallery.ecr.aws/datadog) This gradually rolls out access to new injector and tracer library releases to subsets of customers, with the ability to pause if issues are detected.
Release on: 2025-09-15
Released on: 2025-09-15 Pinned to datadog-agent v7.70.2: CHANGELOG.
Release on: 2025-09-10
Released on: 2025-09-10 Pinned to datadog-agent v7.70.1: CHANGELOG.
Release on: 2025-09-03
autoconfig_exclude_features configuration flag in your datadog.yaml file.gpu.enabled to agent config to control the GPU Core-Check component, disabled by default.1.24.6.datadog.snmp.requests metric, which tracks the number of SNMP requests sent by the Agent to devices.ERROR_INSTALL_SERVICE_FAILURE).ERROR_INSTALL_SERVICE_FAILURE) and causes Error 1719. The Windows Installer Service could not be accessed.enable_stream_payload_serializationenable_service_checks_stream_payload_serializationenable_events_stream_payload_serializationenable_sketch_stream_payload_serializationprometheus_scrape.enabled option is set to true and the pod has a prometheus.io/port annotation, containers must expose that port in their spec in order for the Agent to schedule openmetrics checks.DDAGENTUSER_NAME=NT AUTHORITY\SYSTEM.\\.\pipe\dd_system_probe. This log message was added in Agent 7.63.0. The error is still logged if it persists long enough, see [#35790](https://github.com/DataDog/datadog-agent/pull/35790). Each failed connection attempt still logs the error at debug level to aid troubleshooting.Released on: 2025-09-03 Pinned to datadog-agent v7.70.0: CHANGELOG.
leader_election_default_resource option, the Datadog Cluster Agent no longer creates an unused config map.cronjob.on_schedule_check service check of the kubernetes_state check for CronJobs that have a specific time zone.Release on: 2025-08-27
Released on: 2025-08-27 Pinned to datadog-agent v7.69.4: CHANGELOG.
Release on: 2025-08-26
1.24.6.Released on: 2025-08-26 Pinned to datadog-agent v7.69.3: CHANGELOG.
Release on: 2025-08-20
Released on: 2025-08-20 Pinned to datadog-agent v7.69.2: CHANGELOG.
Release on: 2025-08-18
Remote Agent updates on Windows now checks if the custom Agent password is available before updating the Agent. This prevents the update from failing later and leaving the host without an Agent installed.
This is only applicable to domain-joined hosts using a custom Agent username and password. See [Agent 7.66.0 upgrade notes](https://github.com/DataDog/datadog-agent/releases/tag/7.66.0) for more information.
Released on: 2025-08-18 Pinned to datadog-agent v7.69.1: CHANGELOG.
Release on: 2025-08-14
JAVA_TOOL_OPTIONS that JMXFetch uses by setting the jmx_java_tool_options configuration option in the datadog.yaml config file. This allows you to pass additional JVM options to JMXFetch, such as memory settings or system properties.include_ephemeral_containers to collect Kubernetes ephemeral containers. The option is disabled by default. When enabled, the Agent will report container.* and kubernetes.* metrics for ephemeral containers. It will also collect logs and schedule checks for ephemeral containers when configured to do so.1.24.5.ERROR_INSTALL_ALREADY_RUNNING).install_info from setup scripts. When using Fleet Automation setup scripts, the subsequent MSI installation now skips writing install_info via a new SKIP_INSTALL_INFO flag, preserving the original setup script installation method tracking.agent.exe from the Windows containerReleased on: 2025-08-14 Pinned to datadog-agent v7.69.0: CHANGELOG.
service, env, or version), the webhook will also add the corresponding UST environment variable to the pod (DD_SERVICE, DD_ENV, or DD_VERSION).DD_ADMISSION_CONTROLLER_AUTO_INSTRUMENTATION_INIT_SECURITY_CONTEXT.Release on: 2025-07-28
1.24.5.The Agent MSI no longer fails when it is unable to read the version information from [MsiGetProductInfo](https://learn.microsoft.com/en-us/windows/win32/api/msi/nf-msi-msigetproductinfow).
When upgrading from an Agent version earlier than 7.56, a failure in MsiGetProductInfo, combined with an MSI rollback, may result in missing system drivers. If this occurs, repairing or reinstalling the Agent will restore the missing drivers. This issue is typically caused by a corrupted Windows Installer registry. To repair these issues, refer to the [Microsoft Program Install and Uninstall Troubleshooter](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d).
Released on: 2025-07-28 Pinned to datadog-agent v7.68.3: CHANGELOG.
Release on: 2025-07-21
Released on: 2025-07-21 Pinned to datadog-agent v7.68.2: CHANGELOG.
Release on: 2025-07-17
Released on: 2025-07-17 Pinned to datadog-agent v7.68.1: CHANGELOG.
Release on: 2025-07-10
use_networkv2_check in your configuration.agent configcheck --verbose command and flares now include a section that lists all collected configurations, both matched and unmatched. This addition aids debugging by revealing which configurations the Agent has detected.1.24.4.stop-service Agent subcommand and remote updates now wait longer for the Agent and its subservices to stop before reporting an error.Datadog Installer service on Windows is now set to manual start. This prevents alerts from tools that monitor automatically started services, such as the Windows Server Manager Dashboard.Released on: 2025-07-10 Pinned to datadog-agent v7.68.0: CHANGELOG.
kube_cronjob_status_last_successful_time metric. The name of the metric is kubernetes_state.cronjob.duration_since_last_successful.timeZone field of the CronJob objects in the kubernetes_state.cronjob.on_schedule_check service check.