Refer: https://github.com/DataDog/datadog-agent/releases/tag/7.67.0$$$$$$Agent$$$Prelude$$$Release on: 2025-06-18$$$$$$Please refer to the 7.67.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Bump the Python version to 3.12.11$$$Upgraded JMXFetch to 0.49.7 <https://github.com/DataDog/jmxfetch/releases/0.49.7> which switches from snakeyaml to snakeyaml-engine; adding support for YAML 1.2. See 0.49.7 <https://github.com/DataDog/jmxfetch/releases/tag/0.49.7> for more details.$$$In order to avoid unnecessary DNS queries; the agent now uses FQDN when connecting to Datadog intakes. Specifically; it adds a trailing dot at the end of the Datadog intake hostnames. While most users may not notice this change; it can affect setups where connections between the agent and Datadog intakes are intercepted for deep packet inspection or TLS man-in-the-middle by proxies or firewalls. Users that have such a proxy or L7 firewall should ensure that the rules for agent connections to *.datadoghq.com hosts are also valid for connections to *.datadoghq.com. (with an additional trailing dot) hosts.$$$Update go-sqllexer to 0.1.6.

Upgrade Notes$$$If you use a custom Agent username and password on Windows with an Active Directory domain account and you want to remotely upgrade the Agent using Fleet Automation then you must provide the DDAGENTUSER_PASSWORD option when upgrading to 7.66 or later. For more information see the features release notes.$$$New Features$$$Added a new WLAN check that monitors the Wi-Fi interface on the host system. This check is only available for macOS systems.$$$$$$Fleet Automation now supports remote upgrades when using a custom Agent username and password on Windows.$$$$$$Windows stores the password as an encrypted LSA local private data object that is only accessible to local Administrators. Windows Service Manager stores service account passwords in the same location. For more information; see the Microsoft documentation on Storing Private Data and Private Data Objects.$$$$$$Uninstalling the Agent removes the encrypted password from the LSA.$$$$$$To avoid providing and manually managing the account password; consider using a Group Managed Service Account (gMSA). For more information; see Installing the Agent with a gMSA account.

Agent$$$Prelude$$$Release on: 2025-05-13$$$Please refer to the 7.65.2 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$(datadog-fips-agent) Ensure the post-install script always rebuilds fipsmodule.cnf in case the embedded OpenSSL is updated.$$$The embedded OpenSSL on Windows no longer links against zlib (which wasnt included); preventing errors related to accidentally loading a version of zlib installed on the host.$$$On Windows; restarting the datadogagent service now also restarts the Datadog Installer service to ensure configuration changes take effect.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-05-13 Pinned to datadog-agent v7.65.2: CHANGELOG.$$$Bug Fixes$$$Fix wrong computation of the init container resources in the autoinstrumentation webhook.

7.65.1 $$$Agent$$$Prelude$$$Release on: 2025-05-08$$$Please refer to the 7.65.1 tag on integrations-core for the list of changes on the Core Checks$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-05-08 Pinned to datadog-agent v7.65.1: CHANGELOG.$$$Bug Fixes$$$Customers relying on the deprecated v1 implementation of the auto instrumentation webhook will no longer be forced to use the v2 implementation. This will provide additional time for customers to migrate to the v1 implementation and ensure the v2 implementation adequately supports all existing use cases.

7.65.0 Latest$$$Agent$$$Prelude$$$Release on: 2025-05-06$$$$$$Please refer to the 7.65.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Covers more gRPC status code values sent by tracer libraries$$$Aggregate APM stats payloads by gRPC code$$$New Features$$$The Agent MSI for Windows now installs the .NET APM Instrumentation libraries and automatically configures APM Instrumentation for IIS. To enable this feature; specify the following properties in the MSI command line:$$$$$$DD_APM_INSTRUMENTATION_ENABLED=iis DD_APM_INSTRUMENTATION_LIBRARIES=dotnet:3$$$$$$Requires IIS 10.0 or later. For more information see [Single Step APM Instrumentation](https://docs.datadoghq.com/tracing/trace_collection/automatic_instrumentation/single-step-apm/).$$$$$$APM: Added new OpenLineage event proxy endpoint.$$$$$$A new implementation of auto multi-line detection for logs is now available. This new implementation is more flexible and powerful than the previous one. It now supports arbitrary timestamps; continuous matching; and more flexible configuration. It will be enabled automatically when logs_config.auto_multi_line_detection is set to true. You can opt out of the new implementation by setting logs_config.force_auto_multi_line_detection_v1 to true.$$$$$$APM: Container-based primary tags are now available by default.$$$$$$Enhancement Notes$$$Add a new host tag called orch_cluster_id that is set to the Kubernetes cluster ID generated by the cluster-agent. This is added only for the hosts that are part of a Kubernetes cluster. This tag is also used on every cluster-level resources like kubernetes_state.* metrics; kubernetes events; and orchestrator level resources.$$$$$$Add admission.datadoghq.com/apm-inject.debug: true annotation to inject DD_APM_INSTRUMENTATION_DEBUG=true; DD_TRACE_STARTUP_LOGS=true and DD_TRACE_DEBUG=true to an application container. This is useful for debugging Single Step Instrumentation or tracer issues in Kubernetes environments.$$$$$$Add metrics origins for Sonatype Nexus; Silverstripe CMS and Anecdote integrations.$$$$$$Add the propagate_agent_tags setting. When set to true; the tags from the Agent host are added to the checks tag for all instances.$$$$$$Agents are now built with Go 1.23.7.$$$$$$Agents are now built with Go 1.23.8.$$$$$$Allow integrations to self-declare as HA Supported.$$$$$$Improved trace context creation from Step Function execution context:$$$$$$Now utilizes State.RetryCount and Execution.RedriveCount to generate parent IDs deterministically; preventing collisions with retry spans.$$$Supports multi-level trace merging; allowing an arbitrary number of Lambda and Step Function traces to be linked together while maintaining root context.$$$This update brings feature parity with Node and Python Lambda layers in the Universal runtimes.$$$$$$The hostname subcommand for the Agent now tries to reach out to the running Agent; and falls back to computing the hostname locally if the Agent is not running. You can use the --local option to force the local computation.$$$$$$Cisco SD-WAN: improve memory usage.$$$$$$Adds a metadata_ip_resolution_from_hostname config option to use hostname DNS resolution as the preferred method to compute the host IP address$$$$$$Metrics are now sent over HTTP/2 when possible. A slight change to the connection handling to take full advantage of this means multiple requests can be in flight at any one time. This can be configured with the forwarder_max_concurrent_requests option; default is 10.$$$$$$Added configurations network_path.collector.source_excludes and network_path.collector.dest_excludes; which allow ignoring CIDR ranges in the Network Path collector.$$$$$$Added support for querying the pod list through the API server. This feature; enabled by setting kubeletUseApiServer to true; allows the Agent to retrieve pod metadata directly from the API server instead of the kubelet. This resolves issues when direct access to the kubelet /pods endpoint is restricted. The agent will continue

Agent$$$Prelude$$$Release on: 2025-04-10$$$Enhancement Notes$$$Agents are now built with Go 1.23.8.$$$Bug Fixes$$$Add a configuration option; enable_nvml_detection; disabled by default; to stop the Agent from trying to find the NVML library on startup.$$$Fix remote tagger initialization log message to be logged only once.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-04-10 Pinned to datadog-agent v7.64.3: https://github.com/DataDog/datadog-agent/blob/main/CHANGELOG.rst#7643

7.64.2 -Agent$$$Prelude$$$Please refer to the 7.64.2 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$Process Agent files are added to the flare archive instead of displaying no session token provided.

Agent$$$Prelude$$$Release on: 2025-03-20$$$$$$Please refer to the 7.64.1 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$Fixed Python package dependency issue preventing integrations from loading on Windows$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-03-20 Pinned to datadog-agent v7.64.1: CHANGELOG

7.63.3 Latest$$$Agent$$$Prelude$$$Release on: 2025-03-04$$$$$$Please refer to the 7.63.3 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$Fully disable the X25519Kyber768Draft00 key exchange mechanism to avoid issues with firewalls not supporting multi-packet key exchanges; in particular AWS Network Firewall and Suricata.

Agent$$$Prelude$$$Released on: 2025-02-03$$$$$$Bug Fixes$$$Fixes a connection tracking regression in the 7.62 Fargate preview for Cloud Network Monitoring.

Agent$$$Prelude$$$Release on: 2025-01-13$$$$$$Please refer to the 7.61.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgraded JMXFetch to 0.49.6 which fixes a NullPointerException on JBoss when user and password not set. See 0.49.6 for more details.$$$Windows containers were updated to use OpenJDK 11.0.25+9.$$$New Features$$$Add metrics origins for Nvidia Nim integration.$$$APM: New configuration apm_config.obfuscation.credit_cards.keep_values (DD_APM_OBFUSCATION_CREDIT_CARDS_KEEP_VALUES) can be used to skip specific tag keys that are known to never contain credit card numbers. This is especially useful in cases where a span tag value is a number that triggers false positives from the credit card obfuscator.$$$Add new metric; container.restarts; which indicates the number of times a container has been restarted due to the restart policy. For more details: https://docs.docker.com/engine/containers/start-containers-automatically/.$$$APM: Introducing the Error Tracking Standalone config option. Only span chunks that contain errors or exception OpenTelemetry span events are taken into consideration by sampling.$$$Add new windows images for LTSC 2019 and LTSC 2022:$$$datadog-agent:7-servercore-ltsc2019-amd64$$$datadog-agent:7-servercore-ltsc2022-amd64$$$datadog-agent:7-servercore-ltsc2019-jmx-amd64$$$datadog-agent:7-servercore-ltsc2022-jmx-amd64$$$datadog-agent:latest-servercore-ltsc2019-jmx$$$datadog-agent:latest-servercore-ltsc2022-jmx$$$datadog-agent:latest-servercore-ltsc2019$$$datadog-agent:latest-servercore-ltsc2022$$$datadog-agent:7.X.Y-ltsc2019$$$datadog-agent:7.X.Y-ltsc2022$$$datadog-agent:7.X.Y-ltsc2019-jmx$$$datadog-agent:7.X.Y-ltsc2022-jmx$$$datadog-agent:7.X.Y-servercore-ltsc2019$$$datadog-agent:7.X.Y-servercore-ltsc2022$$$datadog-agent:7.X.Y-servercore-ltsc2019-jmx$$$datadog-agent:7.X.Y-servercore-ltsc2022-jmx$$$datadog-agent:latest-ltsc2019$$$datadog-agent:latest-ltsc2022$$$[ha-agent] Add haagent component used for HA Agent feature.$$$The cluster-agent now can collect pod disruption budgets from the cluster.$$$Added support for collecting container image metadata when running on a CRI-O runtime.$$$USM now monitors TLS traffic encrypted with Go TLS by default. To disable this feature; set the service_monitoring_config.tls.go.enabled configuration option to false.$$$USM now monitors traffic encrypted with Istio mTLS by default. To disable this feature; set the service_monitoring_config.tls.istio.enabled configuration option to false.$$$Introduced a new configuration variable logs_config.http_protocol; allowing users to enforce HTTP/1.1 for outgoing HTTP connections in the Datadog Agent. This provides better control over transport protocols and improves compatibility with systems that do not support HTTP/2. By default; the log agent will now attempt to use HTTP/2 (unless a proxy is configured) and fall back to the best available protocol if HTTP/2 is not supported.$$$Added a new feature flag enable_operation_and_resource_name_logic_v2 in DD_APM_FEATURES. Enabling this flag modifies the logic for computing operation and resource names from OTLP spans to produce shorter; more readable names and improve alignment with OpenTelemetry specifications.$$$Add support for PHP Single Step Instrumentation in Kubernetes (not enabled by default)$$$Enhancement Notes$$$[ha-agent] Run HA enabled integrations only on leader Agent$$$[ha-agent] Add agent_group tag to datadog.agent.running metric$$$Cluster Agent: DatadogAgent custom resource; cluster Agent deployment; and node Agent daemonset manifests are now added to the flare archive when the Cluster Agent is deployed with the Datadog Operator (version 1.11.0+).$$$Add new host tag provider_kind from the value of DD_PROVIDER_KIND for Agents running in GCE.$$$Add query_timeout to customize the timeout for queries in the Oracle check. Previously; this was fixed at 20;000 seconds.$$$Add ability to show Agent telemetry payloads to be sent by Agent if the telemetry is enabled. One can run it with

7.60.1$$$Prelude$$$Release on: 2024-12-19$$$Security Notes$$$Update golang.org/x/crypto to fix CVE-2024-45337.

Release Notes$$$7.60.0$$$Prelude$$$Release on: 2024-12-16$$$$$$Please refer to the 7.60.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Parameter peer_tags_aggregation (a.k.a. environment variable DD_APM_PEER_TAGS_AGGREGATION) is now enabled by default. This means that aggregation of peer related tags (e.g.; peer.service; db.instance; etc.) now happens in the Agent; which enables statistics for Inferred Entities. If you want to disable this feature; set peer_tags_aggregation to false in your Agent configuration.$$$$$$Parameter compute_stats_by_span_kind (a.k.a. environment variable DD_APM_COMPUTE_STATS_BY_SPAN_KIND) is now enabled by default. This means spans with an eligible span.kind will have stats computed. If disabled; only top-level and measured spans will have stats computed. If you want to disable this feature; set compute_stats_by_span_kind to false in your Agent configuration.$$$$$$Note: When using peer_tags_aggregation and compute_stats_by_span_kind; a high cardinality of peer tags or APM resources can contribute to higher CPU and memory consumption. If enabling both causes the Agent to consume too many resources; try disabling compute_stats_by_span_kind first.$$$$$$It is recommended that you update your tracing libraries according to the instructions here and set DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED (or dd.trace.remove.integration-service-names.enabled) to true.$$$$$$Upgraded JMXFetch to 0.49.5 which adds support for UnloadedClassCount metric and IBM J9 gc metrics. See 0.49.5 for more details.$$$$$$New Features$$$Inferred Service dependencies are now Generally Available (exiting Beta) and enabled by default. Inferred Services of all kinds now have trace metrics and are available in dependency maps. apm_config.peer_tags_aggregation and apm_config.compute_stats_by_span_kind both now default to true unless explicitly set to false.$$$$$$Add check_tag_cardinality parameter config check.$$$$$$By default check_tag_cardinality is not set which doesnt change the behavior of the checks. Once it is set in pod annotaions; it overrides the cardinality value provided in the base agent configuration. Example of usage:$$$$$$ad.datadoghq.com/redis.checks: |$$$ {$$$ redisdb: {$$$ check_tag_cardinality: high;$$$ instances: [$$$ {$$$ host: %%host%%;$$$ port: 6379$$$ }$$$ ]$$$ }$$$ } $$$Added a new feature flag enable_receive_resource_spans_v2 in DD_APM_FEATURES that gates a refactored implementation of ReceiveResourceSpans for OTLP.$$$Enhancement Notes$$$Added information about where the Agent sourced BTF data for eBPF to the Agent flare. When applicable; this will appear in system-probe/ebpf_btf_loader.log.$$$The Agent flare now returns NAT debug information from conntrack in the system-probe directory.$$$The flare subcommand includes a --provider-timeout option to set a timeout for each file collection (default is 10s); useful for unblocking slow flare creation.$$$This change reduces the number of DNS queries made by Network Traffic based paths in Network Path. A cache of reverse DNS lookups is used to reduce the number of DNS queries. Additionally; reverse DNS lookups are now performed only for private IPs and not for public IPs.$$$Agent flare now includes system-probe telemetry data via system-probe/system_probe_telemetry.log.$$$The MSI installer uses 7zr to decompress the embedded Python.$$$On Windows; the endpoint /windows_crash_detection/check has been modified to report crashes in an asynchronous manner; to allow processing of large crash dumps without blocking or timing out. The first check will return a busy status and continue to do so until the processing is completed.$$$Deprecation Notes$$$Prebuilt eBPF for the network tracer system-probe module has been deprecated in favor of CO-RE and runtime compilation variants on Linux kernel versions 6+ and RHEL kernel versions 5.14+. To continue to use the prebuilt eBPF n

7.59.1 Latest$$$@kacper-murzyn kacper-murzyn released this 2 days ago$$$· 1211 commits to main since this release$$$ 7.59.1$$$ 3638fcd $$$Prelude$$$Release on: 2024-12-02$$$$$$Enhancement Notes$$$Setting up a temporary directory for JMXFetch to use when it runs. Using the same one the Agent uses when running as this guarantees a directory where JMXFetch can write to. This helps when JMXFetch sends metrics over Unix Domain Socket <https://docs.datadoghq.com/developers/dogstatsd/unix\_socket/?tab=host> as it needs access to a temp directory which it can write to.

7.59.0 Latest$$$ 7.59.0$$$ b97c906 $$$Agent$$$Prelude$$$Release on: 2024-11-07$$$$$$Please refer to the 7.59.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Removed the deprecated config option otlp_config.debug.loglevel in favor of otlp_config.debug.verbosity:$$$loglevel: debug maps to verbosity: detailed$$$loglevel: info maps to verbosity: normal$$$loglevel: warn/error maps to verbosity: basic$$$loglevel: disabled maps to verbosity: none$$$New Features$$$Add ability to run process/container collection on the core Agent (Linux only). This is controlled by the process_config.run_in_core_agent.enabled option in datadog.yaml.$$$DBM: Add configuration options to SQL obfuscator to customize the obfuscation of SQL statements:$$$KeepJSONPath - option to control whether JSON paths following JSON operators in SQL statements should be obfuscated. This option is only valid when ObfuscationMode is obfuscate_and_normalize.$$$APM: Add new sqllexer feature flag for the Trace Agent; which enables the sqllexer imprementation of the SQL Obfuscator.$$$Introduce new Kubernetes tag gpu_vendor for the GPU resource requested by a container.

7.58.1 Latest$$$@kacper-murzyn kacper-murzyn released this 4 days ago$$$· 797 commits to main since this release$$$ 7.58.1$$$ 6f52a65 $$$Agent$$$Prelude$$$Release on: 2024-10-24$$$$$$Enhancement Notes$$$Removes a log statement which was causing a lot of noise in the Network Path logs.$$$Bug Fixes$$$[CWS] Fixes an issue where the cws-instrumentation trace command could panic before launching the traced executable when running on AWS Fargate.$$$[CWS] Fixes an issue where ECS Fargate tags would not be resolved correctly on CWS events.$$$Fixes an error in system-probe triggered by packet capture in environments with multiple VLANs.$$$Fix USMs GO-TLS support for Golang 1.23

7.58.0 Latest$$$Agent$$$Prelude$$$Release on: 2024-10-21$$$$$$Please refer to the 7.58.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Changes behavior of the timeout for Network Path. Previously; the timeout signified the total time to wait for a full traceroute to complete. Now; the timeout signifies the time to wait for each hop in the traceroute. Additionally; the default timeout has been changed to 1000ms.$$$New Features

7.57.2 Latest$$$$$$Prelude$$$Release on: 2024-09-24$$$$$$Enhancement Notes$$$Agents are now built with Go 1.22.7.$$$Bug Fixes$$$Fix OOM error with cluster agent auto instrumentation by increasing default memory request from 20Mi to 100Mi.$$$Fixes a panic caused by running the Agent on readonly filesystems. The Agent returns integration launchers and handles memory gracefully.

Prelude$$$Release on: 2024-09-17$$$$$$Please refer to the 7.57.1 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$APM: When the UDS listener cannot be created on the trace-agent; the process will log the error; instead of crashing.$$$Fixes memory leak caused by container check.

Known bugs$$$ECS Fargate deployments may cause increases in RAM and CPU usage. For more information see #27523.$$$Prelude$$$Release on: 2024-09-09$$$$$$Please refer to the 7.57.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Update cURL to 8.9.1.$$$Update OpenSSL from 3.0.14 to 3.3.1 (on Linux and macOS).$$$New Features$$$The agent diagnose command now includes a --json option to output the results in JSON format.$$$Add integration value for device metadata.$$$APM: In order to allow for automatic instrumentation to work in Kubernetes clusters that enforce a Restricted Pod Security Standard; which require all containers to explicitly set a securityContext; an option to configure a securityContext to be used for all initContainers created by the auto instrumentation has been added. | This can be done through the DD_ADMISSION_CONTROLLER_AUTO_INSTRUMENTATION_INIT_SECURITY_CONTEXT environment value; or admission_controller.auto_instrumentation.init_security_context configuration -in both cases a json string should be supplied.$$$Adds a kube_runtime_class tag to metrics associated with Kubernetes pods and their containers.$$$Expose the Agents get host tags function to python checks using the new datadog_agent.get_host_tags method.$$$Implement static allowlist of Kubernetes events to send by default. This feature is only enabled when filtering_enabled is set to true in the kubernetes_apiserver integration configuration.$$$Adds a new launcher to handle incoming logs from integtrations.$$$Add optional reverse DNS enrichment of private IP addresses to NDM NetFlow.$$$On Windows; the default value for the service inference feature is now enabled.$$$Enhancement Notes$$$Turn on Orchestrator Explorer by default in the core agent$$$Added new source_host tag to TCP/UDP logs to help users understand where their logs came from.$$$Added support to handling UDP/TCP Logs when running the containerized agent.$$$APM: Allow custom HTTP client to be provided when instantiating the trace-agent configuration. This feature is primarily intended for the OpenTelemetry exporter.$$$APM: Add default UDS listeners for traces (trace-agent) and dogstatsd (core-agent) on /var/run/datadog/apm.socket and /var/run/datadog/dsd.socket; respectively. These are used in the Single Step APM Instrumentation; improving the onboarding experience and minimizing the agent configuration.$$$For the [Inferred Service Dependencies beta](https://docs.datadoghq.com/tracing/guide/inferred-service-opt-in/?tab=java); add two new peer.hostname precursor attributes; out.host and dns.hostname. This will improve coverage of inferred services because some tracer integrations only place the peer hostname in one of those attributes.$$$APM stats for internal service overrides are now aggregated by the _dd.base_service tag only; enhancing visibility into specific base services.$$$Include spans with span.kind=consumer for aggregation of stats on peer tags.$$$IP address quantization on all peer tags is done the backend during ingestion. This change updates the Agent to apply the same IP address quantization. This reduces unnecessary aggregation that is currently done on raw IP addresses. And therefore; improves the aggregation performance of stats on peer tags.$$$APM: Add new setting to disable the HTTP receiver in the trace-agent. This setting should almost never be disabled and is only a convenience parameter for OpenTelemetry extensions. Disabling the receiver is semantically equivalent to setting the receiver_port to 0 and receiver_socket to .$$$Agents are now built with Go 1.22.6.$$$[NDM] Adds the option to collect BGP neighbors metrics from Cisco SD-WAN.$$$[NDM] Add option to collect cloud application metrics from Cisco SD-WAN.$$$[Cisco SD-WAN] Allow enabling/disabling metrics collection.$$$Report the hostname of Kubernetes events based on the associated pod that the event relates to.$$$Introduces a parser to extract tags from integration logs and attach them to outgoing logs.$$$Im