Datadog Agent x64 Version 7.80.1.0
Prelude$$$-------$$$$$$Released on: 2026-06-12$$$$$$- Please refer to the `7.80.1 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7801>`_ for the list of changes on the Core Checks$$$$$$$$$.. _Release Notes_7.80.1_Enhancement Notes:$$$$$$Enhancement Notes$$$-----------------$$$$$$- The Agents embedded Python has been upgraded from 3.13.13 to 3.13.14$$$
Datadog Agent x64 Version 7.80.0.0
Agent$$$Prelude$$$Released on: 2026-06-11$$$$$$Please refer to the 7.80.0 tag on integrations-core (https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7800) for the list of changes on the Core Checks$$$Upgrade Notes$$$Health Platform: the ReportIssue method now takes a single IssueReport argument instead of (checkID; checkName string; report *IssueReport). The IssueReport struct carries three new fields — IssueID (unique instance id); IssueType (template id); and Source (reporting integration name) — replacing the separate checkID and checkName arguments.$$$$$$The health platform persistence file format has been bumped to version 2. Existing persistence files (<run_path>/health-platform/issues.json) written by a previous agent version will be detected; logged as incompatible; and discarded on startup; the agent starts with a fresh issue state. No data migration is performed.$$$$$$For integrations calling ReportIssue: construct an IssueReport with IssueID set to a unique instance key (e.g. check-execution-failure:<check-id>); IssueType set to the template identifier that was previously passed as the IssueId field of the proto IssueReport; and Source set to the integration name. To resolve an issue; call ResolveIssue(issueID) instead of passing nil to ReportIssue.$$$$$$Health Platform: the health_platform.issues_detected telemetry counter is now tagged with issue_type instead of health_check_id. Update any dashboards; monitors; or telemetry configuration that filtered or grouped by the health_check_id tag to use issue_type instead.$$$$$$APM: On Linux; the trace agent process now only starts once data is sent to any of its configured listeners.$$$$$$Previously; the trace agent started immediately on agent startup; it now starts lazily when needed; which reduces resource usage. To disable and restore the previous behavior; set apm_config.socket_activation.enabled: false in datadog.yaml; or set the environment variable DD_APM_SOCKET_ACTIVATION_ENABLED=false.$$$$$$New Features$$$The Windows MSI installer now ships the AI usage Chrome native messaging host (ai-prompt-logger-native-host) under bin\agent. The installer generates a Chrome Native Messaging Host manifest under bin\agent\dist and registers it machine-wide under HKLM\SOFTWARE\Google\Chrome$$$ativeMessagingHosts (including the WOW6432Node view for 32-bit Chrome). The hosts runtime configuration is generated as C:\ProgramData\Datadog\ai_usage_native_host.yaml and uses the Agents configured APM receiver port.$$$$$$Adds a new discovery.service_map.enabled system-probe configuration option that boots the universal service monitoring (USM) eBPF monitor in a restricted mode; capturing only the data needed to render a service dependency map (HTTP and HTTPS via TLS uprobes). Hosts running in this mode are not billed as USM customers; are not surfaced in USM dashboards; and do not produce universal.http.* metrics. Intended for non-APM customers as a free preview of application observability.$$$$$$Add k8sobjectsreceiver to the DDOT (Datadog Distribution of OpenTelemetry Collector) default manifest; enabling collection of Kubernetes object events and resource states via the OpenTelemetry Collector pipeline.$$$$$$Adds a new action get-resource in kubeactions.$$$$$$The fleet installers agent-package OCI index now contains a FIPS-flavored sibling manifest for each platform; distinguished by the OCI Platform.Variant field. When DD_FIPS_MODE=true is set; the installer downloads the FIPS manifest; otherwise it downloads the base manifest. The package URL is unchanged in both cases.$$$$$$Add a new nccl core check that collects per-rank NCCL collective communication metrics from GPU training and inference workloads.$$$$$$The check listens on a Unix domain socket (default /var/run/datadog/nccl.socket) for JSON events emitted by the NCCL profiler plugin (libnccl-profiler-dd.so) running inside GPU pods. Each event is tagged with rank; collective; n_ranks; kube
Datadog Agent x64 Version 7.79.2.0
Prelude$$$Released on: 2026-06-03$$$$$$Please refer to the 7.79.2 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bumped containerd dependencies to mitigate CVE-2026-46680: github.com/containerd/containerd to v1.7.32 and pinned github.com/containerd/containerd/v2 to v2.0.9 (the EOL v2.1.x line has no fix).$$$Bug Fixes$$$Use the Docker daemons /ping endpoint instead of /info to verify connectivity during DockerUtil initialization. Some daemons emit DefaultAddressPools[].Base values in /info that are not valid CIDRs; which fail the strict netip.Prefix decoding introduced by the moby v29 client and previously caused DockerUtil to fail to initialize. This cascaded into the Docker workloadmeta collector and the Docker core check being unavailable; leading to missing container/image tags on metrics and traces from Docker containers.$$$$$$Fix the Agents Docker integration against Docker daemons that return malformed values in their /info response. The failure was visible in Agent logs as:$$$$$$Docker init error: temporary failure in dockerutil; will retry later:$$$Error reading remote info: netip.ParsePrefix(invalid Prefix): no /$$$When triggered; it prevented the Docker integration from initializing; which cascaded into:$$$$$$missing container and image tags on metrics; traces and logs collected from Docker containers;$$$missing docker_version and docker_swarm entries in host metadata;$$$missing docker_swarm_node_role host tag on Docker Swarm nodes;$$$in containerized deployments without an explicit DD_HOSTNAME; the Agent could refuse to start because the Docker hostname provider could no longer determine a hostname.$$$Add the macOS hardened-runtime Location Services entitlement (com.apple.security.personal-information.location) to signed Agent binaries in order to trigger the system location permission prompt properly.$$$$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2026-06-03 Pinned to datadog-agent v7.79.2: CHANGELOG.$$$$$$Bug Fixes$$$Cluster Agent: Evaluate AppSec sidecar admission webhook match conditions against the deleted object for pod deletion requests.$$$Cluster Agent: Prevent disabled AppSec proxy injection cleanup from enabling the AppSec sidecar admission webhook.
Datadog Agent x64 Version 7.79.2.0
Prelude$$$Released on: 2026-06-03$$$$$$Please refer to the 7.79.2 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bumped containerd dependencies to mitigate CVE-2026-46680: github.com/containerd/containerd to v1.7.32 and pinned github.com/containerd/containerd/v2 to v2.0.9 (the EOL v2.1.x line has no fix).$$$Bug Fixes$$$Use the Docker daemons /ping endpoint instead of /info to verify connectivity during DockerUtil initialization. Some daemons emit DefaultAddressPools[].Base values in /info that are not valid CIDRs; which fail the strict netip.Prefix decoding introduced by the moby v29 client and previously caused DockerUtil to fail to initialize. This cascaded into the Docker workloadmeta collector and the Docker core check being unavailable; leading to missing container/image tags on metrics and traces from Docker containers.$$$$$$Fix the Agents Docker integration against Docker daemons that return malformed values in their /info response. The failure was visible in Agent logs as:$$$$$$Docker init error: temporary failure in dockerutil; will retry later:$$$Error reading remote info: netip.ParsePrefix(invalid Prefix): no /$$$When triggered; it prevented the Docker integration from initializing; which cascaded into:$$$$$$missing container and image tags on metrics; traces and logs collected from Docker containers;$$$missing docker_version and docker_swarm entries in host metadata;$$$missing docker_swarm_node_role host tag on Docker Swarm nodes;$$$in containerized deployments without an explicit DD_HOSTNAME; the Agent could refuse to start because the Docker hostname provider could no longer determine a hostname.$$$Add the macOS hardened-runtime Location Services entitlement (com.apple.security.personal-information.location) to signed Agent binaries in order to trigger the system location permission prompt properly.$$$$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2026-06-03 Pinned to datadog-agent v7.79.2: CHANGELOG.$$$$$$Bug Fixes$$$Cluster Agent: Evaluate AppSec sidecar admission webhook match conditions against the deleted object for pod deletion requests.$$$Cluster Agent: Prevent disabled AppSec proxy injection cleanup from enabling the AppSec sidecar admission webhook.
Datadog Agent x64 Version 7.79.1.0
Agent$$$Prelude$$$Released on: 2026-05-28$$$$$$Please refer to the 7.79.1 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bump github.com/prometheus/prometheus to v0.311.4 to address CVE-2026-42151 and CVE-2026-42154.$$$Bug Fixes$$$Windows: Fix CD-ROM drives being monitored by the disk check since Agent 7.73.0. The diskv2 check now uses the Windows GetDriveType() API to properly detect and exclude CD-ROM drives; matching the behavior of the previous Python disk check. This fixes false alerts on system.disk.in_use for CD-ROM drives with inserted media.$$$Fix a bug in the workload autoscaling controller where annotation-only edits (e.g. autoscaling.datadoghq.com/preview) on a locally-owned DatadogPodAutoscaler were not picked up until the next .spec change or cluster-agent restart; because the controller gated re-sync on .metadata.generation (which annotations do not bump). Toggling burstable mode via the preview annotation now takes effect on the next reconcile.$$$MacOS agent GUI app needs to ignore SIGPIPE to avoid process termination.$$$On macOS; preserve user customizations to system-probe.yaml across Agent upgrades.$$$Fixed a bug on Windows where the NPM TCP failure rate could exceed 100% and climb indefinitely.
Datadog Agent x64 Version 7.79.0.0
7.79.0 Latest$$$@avonengel avonengel released this last week$$$· 1051 commits to main since this release$$$ 7.79.0$$$ 107ed48 $$$Agent$$$Prelude$$$Released on: 2026-05-20$$$$$$Please refer to the 7.79.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgraded JMXFetch to 0.52.0; which adds JMX metrics mappings for Generational Shenandoah GC and introduces the use_canonical_bean_name option to guarantee consistent key property ordering in bean names. See 0.52.0 for more details.$$$On macOS; the Agent now installs as a system-wide LaunchDaemon running under a dedicated _dd-agent service user instead of a per-user LaunchAgent. Existing per-user installations will need to uninstall and reinstall to adopt the new mode. The previous install script is preserved as install_mac_os_v1.sh for versions prior to 7.79.0.$$$New Features$$$Flares now include a connectivity/resolved_endpoints.txt file that lists the IP addresses each configured Datadog intake endpoint hostname resolves to at flare-generation time. This makes it straightforward to determine whether the Agent is using PrivateLink (private IPs) or the public Datadog intake.$$$Added a capacity-type:spot host tag on AWS EC2 Spot instances. The tag is collected from IMDS and added alongside the other EC2 instance info host tags when collect_ec2_instance_info is enabled.$$$Adds cluster agent processing of select actions on kubernetes resources$$$APM: Add a context-aware shutdown API to the trace agent; allowing callers to specify a timeout when waiting for the agent to stop gracefully.$$$Add a native Go core check for the Datadog CSI driver (datadog_csi_driver); replacing the Python OpenMetrics integration. The check scrapes the CSI drivers Prometheus endpoint and submits datadog.csi_driver.node_publish_volume_attempts.count and datadog.csi_driver.node_unpublish_volume_attempts.count as monotonic count metrics. Metric names; tags; and autodiscovery identifiers are unchanged; no user action is required.$$$Add DNS monitoring support on macOS using libpcap packet capture.$$$Add the comp/dataobs/queryactions agent component for Data Observability query actions. When enabled via data_observability.query_actions.enabled: true; the component subscribes to the DO_QUERY_ACTIONS Remote Configuration product and schedules a do_query_actions Python check to execute SQL queries against monitored Postgres instances on configurable intervals. Results are forwarded to the data-obs-intake.<site>/api/v2/query-actions event platform endpoint.$$$Add agent experimental check-config and agent experimental onboard commands that run a 6-stage validation pipeline on datadog.yaml without requiring a running agent: file permissions; YAML syntax (with line-level error messages); API key format; site/region validity; live API key validation (skippable with --no-api); and a product enablement summary. These commands are experimental and subject to change.$$$On macOS; the Agent now collects CPU L1/L2/L3 cache sizes; CPU package count; and hardware platform in host metadata.$$$Kata core check to gather kata metrics; see details - https://github.com/kata-containers/kata-containers/blob/main/docs/design/kata-2-0-metrics.md#metrics-architecture$$$The macOS install script now accepts DD_INFRASTRUCTURE_MODE to set the Agents infrastructure_mode at install time.$$$Add support for Cloud Network Monitoring (CNM) on macOS via BPF filters.$$$The macOS install script now performs a system-wide installation by default. The Agent runs as a dedicated _dd-agent user via LaunchDaemon.$$$New gauge metric datadog.dogstatsd.offline_duration reports how long (in seconds) the DogStatsD server was offline between the previous shutdown and the current startup. Enable with telemetry.offlinereporter.enabled: true (disabled by default).$$$Enhancement Notes$$$Added support for all public registries to the K8s SSI gradual rollout feature.
Datadog Agent x64 Version 7.79.0.0
7.79.0 Latest$$$@avonengel avonengel released this last week$$$· 1051 commits to main since this release$$$ 7.79.0$$$ 107ed48 $$$Agent$$$Prelude$$$Released on: 2026-05-20$$$$$$Please refer to the 7.79.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgraded JMXFetch to 0.52.0; which adds JMX metrics mappings for Generational Shenandoah GC and introduces the use_canonical_bean_name option to guarantee consistent key property ordering in bean names. See 0.52.0 for more details.$$$On macOS; the Agent now installs as a system-wide LaunchDaemon running under a dedicated _dd-agent service user instead of a per-user LaunchAgent. Existing per-user installations will need to uninstall and reinstall to adopt the new mode. The previous install script is preserved as install_mac_os_v1.sh for versions prior to 7.79.0.$$$New Features$$$Flares now include a connectivity/resolved_endpoints.txt file that lists the IP addresses each configured Datadog intake endpoint hostname resolves to at flare-generation time. This makes it straightforward to determine whether the Agent is using PrivateLink (private IPs) or the public Datadog intake.$$$Added a capacity-type:spot host tag on AWS EC2 Spot instances. The tag is collected from IMDS and added alongside the other EC2 instance info host tags when collect_ec2_instance_info is enabled.$$$Adds cluster agent processing of select actions on kubernetes resources$$$APM: Add a context-aware shutdown API to the trace agent; allowing callers to specify a timeout when waiting for the agent to stop gracefully.$$$Add a native Go core check for the Datadog CSI driver (datadog_csi_driver); replacing the Python OpenMetrics integration. The check scrapes the CSI drivers Prometheus endpoint and submits datadog.csi_driver.node_publish_volume_attempts.count and datadog.csi_driver.node_unpublish_volume_attempts.count as monotonic count metrics. Metric names; tags; and autodiscovery identifiers are unchanged; no user action is required.$$$Add DNS monitoring support on macOS using libpcap packet capture.$$$Add the comp/dataobs/queryactions agent component for Data Observability query actions. When enabled via data_observability.query_actions.enabled: true; the component subscribes to the DO_QUERY_ACTIONS Remote Configuration product and schedules a do_query_actions Python check to execute SQL queries against monitored Postgres instances on configurable intervals. Results are forwarded to the data-obs-intake.<site>/api/v2/query-actions event platform endpoint.$$$Add agent experimental check-config and agent experimental onboard commands that run a 6-stage validation pipeline on datadog.yaml without requiring a running agent: file permissions; YAML syntax (with line-level error messages); API key format; site/region validity; live API key validation (skippable with --no-api); and a product enablement summary. These commands are experimental and subject to change.$$$On macOS; the Agent now collects CPU L1/L2/L3 cache sizes; CPU package count; and hardware platform in host metadata.$$$Kata core check to gather kata metrics; see details - https://github.com/kata-containers/kata-containers/blob/main/docs/design/kata-2-0-metrics.md#metrics-architecture$$$The macOS install script now accepts DD_INFRASTRUCTURE_MODE to set the Agents infrastructure_mode at install time.$$$Add support for Cloud Network Monitoring (CNM) on macOS via BPF filters.$$$The macOS install script now performs a system-wide installation by default. The Agent runs as a dedicated _dd-agent user via LaunchDaemon.$$$New gauge metric datadog.dogstatsd.offline_duration reports how long (in seconds) the DogStatsD server was offline between the previous shutdown and the current startup. Enable with telemetry.offlinereporter.enabled: true (disabled by default).$$$Enhancement Notes$$$Added support for all public registries to the K8s SSI gradual rollout feature.
Datadog Agent x64 Version 7.78.4.0
7.78.4$$$Prelude$$$Released on: 2026-05-14$$$$$$Please refer to the 7.78.4 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Upgrade github.com/moby/spdystream to 0.5.1 to address CVE-2026-35469. In versions 0.5.0 and below; the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count; the header count in parseHeaderValueBlock; and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed; a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2026-05-14 Pinned to datadog-agent v7.78.4: CHANGELOG.
Datadog Agent x64 Version 7.78.4.0
7.78.4$$$Prelude$$$Released on: 2026-05-14$$$$$$Please refer to the 7.78.4 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Upgrade github.com/moby/spdystream to 0.5.1 to address CVE-2026-35469. In versions 0.5.0 and below; the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count; the header count in parseHeaderValueBlock; and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed; a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2026-05-14 Pinned to datadog-agent v7.78.4: CHANGELOG.
Datadog Agent x64 Version 7.78.2.0
7.78.2$$$Prelude$$$Released on: 2026-04-29$$$$$$Please refer to the 7.78.2 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Adds datadog-agent otel command to install/remove DDOT from an OCI package.$$$Deprecation Notes$$$The Install-Datadog.ps1 PowerShell script is deprecated and will be removed in a future version. Please use datadog-installer or the MSI installer instead. Visit the in-app installation guide for complete up-to-date installation instructions.$$$Bug Fixes$$$The signature check in Install-Datadog.ps1 is now more accomodating to formatting variations in the CN field. Refer to the Agent Data Security page for more information on validating signatures.$$$Fixes user-defined network_path.collector.filters being silently dropped when infrastructure_mode is set to end_user_device. Custom filters are now correctly appended to the built-in EUDM defaults.
Datadog Agent x64 Version 7.78.2.0
7.78.2$$$Prelude$$$Released on: 2026-04-29$$$$$$Please refer to the 7.78.2 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Adds datadog-agent otel command to install/remove DDOT from an OCI package.$$$Deprecation Notes$$$The Install-Datadog.ps1 PowerShell script is deprecated and will be removed in a future version. Please use datadog-installer or the MSI installer instead. Visit the in-app installation guide for complete up-to-date installation instructions.$$$Bug Fixes$$$The signature check in Install-Datadog.ps1 is now more accomodating to formatting variations in the CN field. Refer to the Agent Data Security page for more information on validating signatures.$$$Fixes user-defined network_path.collector.filters being silently dropped when infrastructure_mode is set to end_user_device. Custom filters are now correctly appended to the built-in EUDM defaults.
Datadog Agent x64 Version 7.78.0.0
Release Notes$$$=============$$$$$$.. _Release Notes_7.78.0:$$$$$$7.78.0$$$======$$$$$$.. _Release Notes_7.78.0_Prelude:$$$$$$Prelude$$$-------$$$$$$Released on: 2026-04-15$$$$$$- Please refer to the `7.78.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7780>`_ for the list of changes on the Core Checks$$$$$$$$$.. _Release Notes_7.78.0_Upgrade Notes:$$$$$$Upgrade Notes$$$-------------$$$$$$- APM OTLP: Changed attribute precedence behavior when looking up OpenTelemetry semantic convention attributes that have multiple equivalent keys (e.g.; ``http.status_code`` vs ``http.response.status_code``; ``deployment.environment`` vs ``deployment.environment.name``).$$$ $$$ **Previous behavior**: When both old and new semantic convention keys existed; the lookup would check ALL keys in span attributes before checking ANY key in resource attributes. So whichever key appeared in span attributes would win; regardless of which key was in resource attributes.$$$ $$$ **New behavior**: The lookup now uses a per-concept precedence order. For each semantic concept; the registry defines an ordered list of attribute keys; the first key that has a value is returned. The precedence order (which key takes priority) depends on the concept and may prefer either the newer or the older convention key. Span vs resource precedence (which map is checked first) is unchanged and still depends on the function.$$$ $$$ **Who is affected**: This change only affects users who have the same concept represented by different convention-version keys in span vs resource attributes. The returned value may now come from a different key than before; according to the concepts precedence order.$$$ $$$ This is an uncommon configuration since most instrumentation libraries use consistent semantic convention versions across span and resource attributes.$$$$$$$$$.. _Release Notes_7.78.0_New Features:$$$$$$New Features$$$------------$$$$$$- Allows the Agent to get an API key in exchange for an AWS cloud authorization proof.$$$ This allows you to use your AWS credentials against Datadog and removes the$$$ need for you to manage an API key. More details can be found here:$$$ https://docs.datadoghq.com/account_management/cloud_provider_authentication/$$$$$$- The autoscaling vertical controller now supports in-place vertical pod resizing.$$$$$$- Add a new configuration provider; which schedules new instances of KSM checks to generate metrics$$$ from ``CustomResourceDefinitions``.$$$ $$$ This new provider works with the ``kube_crd`` listener which listens for ``CustomResourceDefinitions``$$$ created on the cluster and triggers a new autodiscovery-service for each one.$$$ $$$ This new configuration provider must use the standard kubernetes ``GroupVersionKind`` format in its$$$ ``AdvancedADIdentifier`` section to apply to a matching ``CustomResourceDefinition``.$$$ $$$ The rest of the configuration is a standard KSM configuration instance.$$$$$$- CNM - Add 7 per-connection TCP congestion signals: rto_count (RTO$$$ loss events); recovery_count (fast recovery events); reord_seen$$$ (send-side reordering); rcv_ooopack (receive-side out-of-order$$$ packets); delivered_ce (ECN CE-marked segments); ecn_negotiated$$$ (ECN negotiation status); and probe0_count (zero-window probes).$$$ Collected via eBPF on CO-RE and runtime-compiled tracers; Linux only.$$$$$$- ``dd-procmgrd`` can now read process definitions and manage child process lifecycles with graceful shutdown.$$$$$$- ``dd-procmgrd`` now supervises managed processes with configurable restart policies; exponential backoff; and burst limiting.$$$$$$- ``dd-procmgrd`` can now manage the DDOT (Datadog Distribution of OpenTelemetry) collector process via a dual-mode mechanism. When a ``processes.d/datadog-agent-ddot.yaml`` config is present; ``dd-procmgrd`` takes over DDOT lifecycle management; otherwise the existing systemd unit manages it directly.$$$$$$- Automatic SBOM generation for running containers via
Datadog Agent x64 Version 7.78.0.0
Release Notes$$$=============$$$$$$.. _Release Notes_7.78.0:$$$$$$7.78.0$$$======$$$$$$.. _Release Notes_7.78.0_Prelude:$$$$$$Prelude$$$-------$$$$$$Released on: 2026-04-15$$$$$$- Please refer to the `7.78.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7780>`_ for the list of changes on the Core Checks$$$$$$$$$.. _Release Notes_7.78.0_Upgrade Notes:$$$$$$Upgrade Notes$$$-------------$$$$$$- APM OTLP: Changed attribute precedence behavior when looking up OpenTelemetry semantic convention attributes that have multiple equivalent keys (e.g.; ``http.status_code`` vs ``http.response.status_code``; ``deployment.environment`` vs ``deployment.environment.name``).$$$ $$$ **Previous behavior**: When both old and new semantic convention keys existed; the lookup would check ALL keys in span attributes before checking ANY key in resource attributes. So whichever key appeared in span attributes would win; regardless of which key was in resource attributes.$$$ $$$ **New behavior**: The lookup now uses a per-concept precedence order. For each semantic concept; the registry defines an ordered list of attribute keys; the first key that has a value is returned. The precedence order (which key takes priority) depends on the concept and may prefer either the newer or the older convention key. Span vs resource precedence (which map is checked first) is unchanged and still depends on the function.$$$ $$$ **Who is affected**: This change only affects users who have the same concept represented by different convention-version keys in span vs resource attributes. The returned value may now come from a different key than before; according to the concepts precedence order.$$$ $$$ This is an uncommon configuration since most instrumentation libraries use consistent semantic convention versions across span and resource attributes.$$$$$$$$$.. _Release Notes_7.78.0_New Features:$$$$$$New Features$$$------------$$$$$$- Allows the Agent to get an API key in exchange for an AWS cloud authorization proof.$$$ This allows you to use your AWS credentials against Datadog and removes the$$$ need for you to manage an API key. More details can be found here:$$$ https://docs.datadoghq.com/account_management/cloud_provider_authentication/$$$$$$- The autoscaling vertical controller now supports in-place vertical pod resizing.$$$$$$- Add a new configuration provider; which schedules new instances of KSM checks to generate metrics$$$ from ``CustomResourceDefinitions``.$$$ $$$ This new provider works with the ``kube_crd`` listener which listens for ``CustomResourceDefinitions``$$$ created on the cluster and triggers a new autodiscovery-service for each one.$$$ $$$ This new configuration provider must use the standard kubernetes ``GroupVersionKind`` format in its$$$ ``AdvancedADIdentifier`` section to apply to a matching ``CustomResourceDefinition``.$$$ $$$ The rest of the configuration is a standard KSM configuration instance.$$$$$$- CNM - Add 7 per-connection TCP congestion signals: rto_count (RTO$$$ loss events); recovery_count (fast recovery events); reord_seen$$$ (send-side reordering); rcv_ooopack (receive-side out-of-order$$$ packets); delivered_ce (ECN CE-marked segments); ecn_negotiated$$$ (ECN negotiation status); and probe0_count (zero-window probes).$$$ Collected via eBPF on CO-RE and runtime-compiled tracers; Linux only.$$$$$$- ``dd-procmgrd`` can now read process definitions and manage child process lifecycles with graceful shutdown.$$$$$$- ``dd-procmgrd`` now supervises managed processes with configurable restart policies; exponential backoff; and burst limiting.$$$$$$- ``dd-procmgrd`` can now manage the DDOT (Datadog Distribution of OpenTelemetry) collector process via a dual-mode mechanism. When a ``processes.d/datadog-agent-ddot.yaml`` config is present; ``dd-procmgrd`` takes over DDOT lifecycle management; otherwise the existing systemd unit manages it directly.$$$$$$- Automatic SBOM generation for running containers via
Datadog Agent x64 Version 7.77.2.0
7.77.2$$$Prelude$$$Released on: 2026-04-01$$$$$$Please refer to the 7.77.2 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Hide GUI app by default for MacOS agent per-user install.$$$Windows: Add PAR self-enrollment to installer.$$$Bug Fixes$$$Fixes Workload Protection raw-packet eBPF programs when multiple packet filters are compiled together. The generated assembly reused register R8 both as the event pointer expected by the filter chain and to hold immediate values; which corrupted the pointer and caused the kernel BPF verifier to reject the program. The code now uses a separate register for those immediates so the pointer is preserved across filters.$$$Workload Protection: resolves an issue in in-kernel cgroup tracking; enabling packet filtering to be correctly applied to containers.
Datadog Agent x64 Version 7.77.2.0
7.77.2$$$Prelude$$$Released on: 2026-04-01$$$$$$Please refer to the 7.77.2 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Hide GUI app by default for MacOS agent per-user install.$$$Windows: Add PAR self-enrollment to installer.$$$Bug Fixes$$$Fixes Workload Protection raw-packet eBPF programs when multiple packet filters are compiled together. The generated assembly reused register R8 both as the event pointer expected by the filter chain and to hold immediate values; which corrupted the pointer and caused the kernel BPF verifier to reject the program. The code now uses a separate register for those immediates so the pointer is preserved across filters.$$$Workload Protection: resolves an issue in in-kernel cgroup tracking; enabling packet filtering to be correctly applied to containers.
Datadog Agent x64 Version 7.76.3.0
7.76.3 Latest$$$$$$Agent$$$Prelude$$$Released on: 2026-03-09$$$$$$Please refer to the 7.76.3 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bump github.com/cloudflare/circl to fix v1.6.3 to fix CVE-2026-1229.$$$Fixed a limited out-of-bounds memory read and DoS vulnerability in Windows kernel driver while handling TLS traffic. The host must have the ddnpm kernel driver service running; by having system_probe_config and network_config enabled; to be affected. This configuration is not enabled by default. Query with PowerShell: Get-Service ddnpm Query with command prompt: sc query ddnpm$$$Bug Fixes$$$Fixed IPv6 address matching logic that caused network traffic to be tracked incorrectly. Fixed failed classification of HTTP DELETE requests. Added additional memory handling and overflow safety checks.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2026-03-09 Pinned to datadog-agent v7.76.3
Datadog Agent x64 Version 7.76.3.0
7.76.3 Latest$$$$$$Agent$$$Prelude$$$Released on: 2026-03-09$$$$$$Please refer to the 7.76.3 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bump github.com/cloudflare/circl to fix v1.6.3 to fix CVE-2026-1229.$$$Fixed a limited out-of-bounds memory read and DoS vulnerability in Windows kernel driver while handling TLS traffic. The host must have the ddnpm kernel driver service running; by having system_probe_config and network_config enabled; to be affected. This configuration is not enabled by default. Query with PowerShell: Get-Service ddnpm Query with command prompt: sc query ddnpm$$$Bug Fixes$$$Fixed IPv6 address matching logic that caused network traffic to be tracked incorrectly. Fixed failed classification of HTTP DELETE requests. Added additional memory handling and overflow safety checks.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2026-03-09 Pinned to datadog-agent v7.76.3
Datadog Agent x64 Version 7.75.4.0
Agent$$$Prelude$$$Released on: 2026-02-17$$$$$$Please refer to the 7.75.4 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Agents are now built with Go 1.25.7.$$$Security Notes$$$APM: On span tags; add obfuscation for HELLO and MIGRATE Redis commands.$$$Similar to AUTH; all arguments passed to these commands will be obfuscated and replaced with ?.
Datadog Agent x64 Version 7.75.4.0
Agent$$$Prelude$$$Released on: 2026-02-17$$$$$$Please refer to the 7.75.4 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Agents are now built with Go 1.25.7.$$$Security Notes$$$APM: On span tags; add obfuscation for HELLO and MIGRATE Redis commands.$$$Similar to AUTH; all arguments passed to these commands will be obfuscated and replaced with ?.
Datadog Agent x64 Version 7.74.1.0
Agent$$$Prelude$$$Release on: 2026-01-12$$$$$$Please refer to the 7.74.1 tag on integrations-core (https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7741) for the list of changes on the Core Checks$$$Bug Fixes$$$Fix fatal concurrent map access errors that might occur when system-probe evaluates SSH monitoring security rules.$$$Fix a bug that crashes the Agent when remotely changing the system-probe configuration from Fleet Automation.
Datadog Agent x64 Version 7.74.1.0
Agent$$$Prelude$$$Release on: 2026-01-12$$$$$$Please refer to the 7.74.1 tag on integrations-core (https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7741) for the list of changes on the Core Checks$$$Bug Fixes$$$Fix fatal concurrent map access errors that might occur when system-probe evaluates SSH monitoring security rules.$$$Fix a bug that crashes the Agent when remotely changing the system-probe configuration from Fleet Automation.
Datadog Agent x64 Version 7.73.3.0
7.73.3 $$$Agent$$$Prelude$$$Release on: 2025-12-31$$$$$$Please refer to the 7.73.3 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$Fixed device-mapper (LVM) device tagging in the diskv2 check to match Python psutil behavior. Previously; devices were reported as dm-X (e.g.; device:dm-0) instead of their friendly /dev/mapper/* names (e.g.; device:ocivolume-root). This ensures backward compatibility with the Python disk check and preserves existing dashboards and monitors.$$$$$$Fix an issue introduced in 7.73.0 that can cause the MSI to overwrite the site option in datadog.yaml with the default value of datadoghq.com.$$$$$$This issue impacts users who do not provide the SITE option to the MSI when upgrading AND who have an error in their datadog.yaml file that prevents the MSI from reading the existing site option (MSI log contains ReadConfig. User config could not be read).$$$$$$This issue also impacts users of datadog-installer.exe and Install-Datadog.ps1; introduced in 7.72.0; who do not provide the DD_SITE environment variable
Datadog Agent x64 Version 7.73.2.0
7.73.2$$$Agent$$$Release on: 2025-12-23$$$$$$Bug Fixes$$$The disk check now handles PartitionsWithContext errors gracefully instead of failing entirely. When some partitions fail to load; the check continues collecting metrics for the partitions that succeeded. This aligns the Go implementation with the Python check behavior.$$$The new version of the disk check on Windows now normalizes the device: tag by stripping backslashes and lowercasing; matching the Python disk check behavior. This ensures customers that migrated from Python to Go disk check see consistent device: tag values (e.g.; C:\ becomes c:).$$$Implemented a fix so that the Agent does not try to schedule the orchestrator_kubelet_config check when the orchestrator_explorer.kubelet_config_check.enabled config is set to false.$$$$$$Refer - https://github.com/DataDog/datadog-agent/releases/tag/7.73.2
Datadog Agent x64 Version 7.73.1.0
7.72.4$$$Agent$$$Release on: 2025-12-17$$$Refer - https://github.com/DataDog/datadog-agent/releases/tag/7.73.1
Datadog Agent x64 Version 7.73.1.0
7.72.4$$$Agent$$$Release on: 2025-12-17$$$Refer - https://github.com/DataDog/datadog-agent/releases/tag/7.73.1
Datadog Agent x64 Version 7.72.4.0
7.72.4 $$$Agent$$$Release on: 2025-12-01$$$Please refer -https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7724$$$for the list of changes on the Core Checks
Datadog Agent x64 Version 7.72.4.0
7.72.4 $$$Agent$$$Release on: 2025-12-01$$$Please refer -https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7724$$$for the list of changes on the Core Checks
Datadog Agent x64 Version 7.72.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.72.2
Datadog Agent x64 Version 7.72.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.72.2
Datadog Agent x64 Version 7.72.1.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.72.1
Datadog Agent x64 Version 7.71.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.71.2
Datadog Agent x64 Version 7.71.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.71.2
Datadog Agent x64 Version 7.71.1.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.71.1
Datadog Agent x64 Version 7.71.1.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.71.1
Datadog Agent x64 Version 7.71.1.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.71.1
Datadog Agent x64 Version 7.70.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.2
Datadog Agent x64 Version 7.70.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.2
Datadog Agent x64 Version 7.70.2.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.2
Datadog Agent x64 Version 7.70.1.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.1
Datadog Agent x64 Version 7.70.1.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.1
Datadog Agent x64 Version 7.70.0.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.0
Datadog Agent x64 Version 7.70.0.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.0
Datadog Agent x64 Version 7.70.0.0
Refer the link below for details on the new features; enhancements; and bug fixes in the latest release.$$$https://github.com/DataDog/datadog-agent/releases/tag/7.70.0
Datadog Agent x64 Version 7.69.4.0
7.69.4 Latest$$$Agent$$$Prelude$$$Release on: 2025-08-27$$$$$$Please refer to the 7.69.4 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgrade sqllite to 3.50.4 on Windows.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-08-27 Pinned to datadog-agent v7.69.4: CHANGELOG.
Datadog Agent x64 Version 7.69.4.0
7.69.4 Latest$$$Agent$$$Prelude$$$Release on: 2025-08-27$$$$$$Please refer to the 7.69.4 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgrade sqllite to 3.50.4 on Windows.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-08-27 Pinned to datadog-agent v7.69.4: CHANGELOG.
Datadog Agent x64 Version 7.69.4.0
7.69.4 Latest$$$Agent$$$Prelude$$$Release on: 2025-08-27$$$$$$Please refer to the 7.69.4 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgrade sqllite to 3.50.4 on Windows.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-08-27 Pinned to datadog-agent v7.69.4: CHANGELOG.
Datadog Agent x64 Version 7.69.2.0
7.69.2$$$Agent$$$Prelude$$$Release on: 2025-08-20$$$Please refer to the 7.69.2 tag on integrations-core for the list of changes on the Core Checks - https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7692$$$Upgrade Notes$$$Upgrade libxml2 to 2.14.5.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-08-20 Pinned to datadog-agent v7.69.2 : https://github.com/DataDog/datadog-agent/blob/main/CHANGELOG.rst#7692
Datadog Agent x64 Version 7.69.2.0
7.69.2$$$Agent$$$Prelude$$$Release on: 2025-08-20$$$Please refer to the 7.69.2 tag on integrations-core for the list of changes on the Core Checks - https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7692$$$Upgrade Notes$$$Upgrade libxml2 to 2.14.5.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-08-20 Pinned to datadog-agent v7.69.2 : https://github.com/DataDog/datadog-agent/blob/main/CHANGELOG.rst#7692
Datadog Agent x64 Version 7.69.2.0
7.69.2$$$Agent$$$Prelude$$$Release on: 2025-08-20$$$Please refer to the 7.69.2 tag on integrations-core for the list of changes on the Core Checks - https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7692$$$Upgrade Notes$$$Upgrade libxml2 to 2.14.5.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-08-20 Pinned to datadog-agent v7.69.2 : https://github.com/DataDog/datadog-agent/blob/main/CHANGELOG.rst#7692
Datadog Agent x64 Version 7.68.3.0
7.68.3$$$$$$Agent$$$Prelude$$$Release on: 2025-07-28$$$$$$Please refer to the 7.68.3 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgraded JMXFetch to 0.49.9 <https://github.com/DataDog/jmxfetch/releases/0.49.9> which reverts a change that broke support for Java 7. See 0.49.9 <https://github.com/DataDog/jmxfetch/releases/tag/0.49.9> for more details.$$$Enhancement Notes$$$Agents are now built with Go 1.24.5.$$$Bug Fixes$$$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).
Datadog Agent x64 Version 7.68.3.0
7.68.3$$$$$$Agent$$$Prelude$$$Release on: 2025-07-28$$$$$$Please refer to the 7.68.3 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Upgraded JMXFetch to 0.49.9 <https://github.com/DataDog/jmxfetch/releases/0.49.9> which reverts a change that broke support for Java 7. See 0.49.9 <https://github.com/DataDog/jmxfetch/releases/tag/0.49.9> for more details.$$$Enhancement Notes$$$Agents are now built with Go 1.24.5.$$$Bug Fixes$$$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).
Datadog Agent x64 Version 7.68.2.0
7.68.2$$$$$$Agent$$$Prelude$$$Release on: 2025-07-21$$$$$$Please refer to the 7.68.2 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$Fix an issue with the Agent pre-install script that caused integrations shipped with the Agent to be removed during an Agent upgrade.$$$Print the correct FIPS status for the Cluster Agent when running in FIPS mode.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-07-21 Pinned to datadog-agent v7.68.2: CHANGELOG.
Datadog Agent x64 Version 7.68.2.0
7.68.2$$$$$$Agent$$$Prelude$$$Release on: 2025-07-21$$$$$$Please refer to the 7.68.2 tag on integrations-core for the list of changes on the Core Checks$$$Bug Fixes$$$Fix an issue with the Agent pre-install script that caused integrations shipped with the Agent to be removed during an Agent upgrade.$$$Print the correct FIPS status for the Cluster Agent when running in FIPS mode.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-07-21 Pinned to datadog-agent v7.68.2: CHANGELOG.
Datadog Agent x64 Version 7.68.1.0
7.68.1$$$Prelude$$$Release on: 2025-07-17$$$$$$Please refer to the 7.68.1 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bump the secret-generic-connector side binary to 0.2.5
Datadog Agent x64 Version 7.68.1.0
7.68.1$$$Prelude$$$Release on: 2025-07-17$$$$$$Please refer to the 7.68.1 tag on integrations-core for the list of changes on the Core Checks$$$Security Notes$$$Bump the secret-generic-connector side binary to 0.2.5
Datadog Agent x64 Version 7.68.0.0
7.68.0$$$Agent$$$Prelude$$$Release on: 2025-07-10$$$$$$Please refer to the 7.68.0 tag on integrations-core for the list of changes on the Core Checks$$$Upgrade Notes$$$Bump the Python version to 3.12.11$$$Change how attribute precedence is handled. All fields are now evaluated across both span and resource attributes; using the following order of precedence (from highest to lowest):$$$datadog.* span attributes$$$datadog.* resource attributes$$$standard span attributes$$$standard resource attributes$$$New Features$$$Add a port of the Windows integrations-core Python network check to Go. This version is disabled by default but can be enabled with use_networkv2_check in your configuration.$$$Add support for Autodiscovery for RDS Postgres and MySQL databases.$$$Windows: Add remote certificate collection for the Windows Certificate Store integration.$$$Add a System Probe module that will collect software inventory data from the host.$$$Added logs.truncated and associated aggregate tags into /comp/core/agenttelemetry/impl/config.go$$$Workload protection (CWS) can now generate events based on the setsockopt syscall$$$Added a new logs.truncated metric to the Agent that reports the number of logs truncated before being sent. This metric helps monitor log volume loss due to truncation and is tagged by service and source for better visibility.$$$Enhancement Notes$$$The 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.$$$Adds in newly supported ap2.datadoghq.com site to the MSIs GUI menu.$$$Individual integrations can now set their own auto multiline configurations; including adding custom samples for logs specific to that integration.$$$Allows RDS autodicovery to work with an empty tag list. If an empty tag list is provided; the autodiscovery will not filter instances based on tags; allowing all RDS instances to be discovered.$$$OpenTelemetry instrumentation scope attributes are now converted into log attributes.$$$Introduce a new sample configuration file; application_monitoring.yaml; to support the Hands Off config feature. This file is automatically placed under /etc/datadog-agent/ on Linux systems only. Users can manually edit the file to apply application monitoring configurations.$$$Agents are now built with Go 1.24.4.$$$ecs_cluster_name is added as a global tag when running on EC2.$$$Improve the memory efficiency of obfuscator key generation.$$$In OTLP metrics ingestion; the instrumentation_scope_metadata_as_tags option is now enabled by default. This means scope attributes are now added as tags to metrics. If you have too many unique values for instrumentation scope attributes; this may cause cardinality issues. To mitigate this; you can disable the behavior by setting datadog.metrics.instrumentation_scope_metadata_as_tags to false.$$$Orchestrator manifests will now be published with all tags present in their metadata counterparts.$$$Single Step Instrumentation now uses the Python tracer major version 3 by default.$$$Refactor the logs-agent auditor to utilize a more testable architecture.$$$Add Kind; ApiVersion; and NodeName to manifests. Add HostName to CollectorManifest.$$$Sensitive text from custom resources is now scrubbed from the manifest. If a field is sensitive; all values within that field are automatically redacted; ensuring that sensitive data is not exposed even in nested structures.$$$Update registry writer to not write atomically when Agent runs on ECS Fargate to reduce memory leak.$$$Updated Windows container image labels to align with Linux image labels for better OCI compliance. Added standard Open Container Initiative (OCI) labels including image source; revision; and version information.$$$Bug Fixes$$$APM: Fix an issue where the trace-agent could panic during shutdown trying to obfuscate a SQL payload.$$$APM: Fix an issue where trace-agent could panic with send on closed chan
Datadog Agent x64 Version 7.67.1.0
7.67.1 Latest$$$Agent$$$Prelude$$$Release on: 2025-07-02$$$Please refer to the 7.67.1 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Agents are now built with Go 1.23.10.$$$Bug Fixes$$$Fixes invalid logs compression error in DDOT; sets DDOT logs compression to gzip.$$$Permissions are no longer applied recursively to the Datadog installer data directory on Windows.$$$This fixes an issue that causes Agent updates to restrict access to the .NET APM tracer libraries that were previously installed by the DD_APM_INSTRUMENTATION_LIBRARIES option; preventing them from being loaded by IIS.$$$Fixes an issue in Install-Datadog.ps1 that could malform datadog.yaml and cause the Agent to fail to start. When datadog.yaml does not end with a new line the remote_updates option was incorrectly appended to the last line in the file instead of to a new line.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-07-02 Pinned to datadog-agent v7.67.1: CHANGELOG.
Datadog Agent x64 Version 7.67.1.0
7.67.1 Latest$$$Agent$$$Prelude$$$Release on: 2025-07-02$$$Please refer to the 7.67.1 tag on integrations-core for the list of changes on the Core Checks$$$Enhancement Notes$$$Agents are now built with Go 1.23.10.$$$Bug Fixes$$$Fixes invalid logs compression error in DDOT; sets DDOT logs compression to gzip.$$$Permissions are no longer applied recursively to the Datadog installer data directory on Windows.$$$This fixes an issue that causes Agent updates to restrict access to the .NET APM tracer libraries that were previously installed by the DD_APM_INSTRUMENTATION_LIBRARIES option; preventing them from being loaded by IIS.$$$Fixes an issue in Install-Datadog.ps1 that could malform datadog.yaml and cause the Agent to fail to start. When datadog.yaml does not end with a new line the remote_updates option was incorrectly appended to the last line in the file instead of to a new line.$$$Datadog Cluster Agent$$$Prelude$$$Released on: 2025-07-02 Pinned to datadog-agent v7.67.1: CHANGELOG.
Datadog Agent x64 Version 7.67.0.0
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.
Datadog Agent x64 Version 7.67.0.0
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.
Datadog Agent x64 Version 7.66.0.0
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.
Datadog Agent x64 Version 7.65.2.0
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.
Datadog Agent x64 Version 7.65.1.0
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.
Datadog Agent x64 Version 7.65.0.0
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
Datadog Agent x64 Version 7.64.3.0
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
Datadog Agent x64 Version 7.64.2.0
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.
Datadog Agent x64 Version 7.64.1.0
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
Datadog Agent x64 Version 7.63.3.0
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.
Datadog Agent x64 Version 7.62.1.0
Agent$$$Prelude$$$Released on: 2025-02-03$$$$$$Bug Fixes$$$Fixes a connection tracking regression in the 7.62 Fargate preview for Cloud Network Monitoring.
Datadog Agent x64 Version 7.61.0.0
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
Datadog Agent x64 Version 7.60.1.0
7.60.1$$$Prelude$$$Release on: 2024-12-19$$$Security Notes$$$Update golang.org/x/crypto to fix CVE-2024-45337.
Datadog Agent x64 Version 7.60.0.0
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
Datadog Agent x64 Version 7.59.1.0
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.
Datadog Agent x64 Version 7.59.0.0
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.
Datadog Agent x64 Version 7.58.1.0
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
Datadog Agent x64 Version 7.58.0.0
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
Datadog Agent x64 Version 7.57.2.0
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.
Datadog Agent x64 Version 7.57.1.0
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.
Datadog Agent x64 Version 7.57.0.0
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
Datadog Agent x64 Version 7.57.0.0
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
Datadog Agent x64 Version 7.57.0.0
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
Datadog Agent x64 Version 7.57.0.0
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
