Datadog Release Notes

Agent

Prelude

Released on: 2026-10-07

• Please refer to the 7.84.2 tag on integrations-core for the list of changes on the Core Checks

New Features

• Add Fleet-managed upgrades and rollback for Windows FIPS Agents.

Enhancement Notes

• Allow enabling Private Action Runner split mode during a Windows Agent installation with the DD_PRIVATE_ACTION_RUNNER_SPLIT_ENABLED MSI property.

Security Notes

• Bumped pip to 26.2.1 in the embedded Python distribution.
• Patch the embedded MIT krb5 library so NegoEx GSS token parsing rejects truncated headers and missing extension vectors instead of reading past the buffer.

Bug Fixes

• Fix Kueue pods sometimes missing the kueue_workload, kueue_workload_uid and kueue_resource_flavor tags after an Agent restart.
• Windows Fleet installer setup now rejects standard/FIPS Agent mismatches before stopping the installed Agent, with a message to use the matching installer.

Datadog Cluster Agent

Prelude

Released on: 2026-10-07 Pinned to datadog-agent v7.84.2: CHANGELOG.

Bug Fixes …

Agent

Prelude

Released on: 2026-09-30

• Please refer to the 7.84.0 tag on integrations-core for the list of changes on the Core Checks

Upgrade Notes

• On Linux, the Datadog process manager (dd-procmgrd) is now a first-class service manager alongside systemd, upstart and sysvinit, and it is the default when the dd-procmgrd binary ships with the Agent. The OpenTelemetry Collector distribution is supervised through processes.d and the datadog-agent-ddot systemd unit is no longer installed.

  Each service manager now installs its own self-consistent set of units, so a host runs either the dd-procmgrd supervision path or the per-payload systemd units, never a mix of the two.

• Linux Agent packages no longer include the static archive /opt/datadog-agent/embedded/lib/libpcap.a. This affects users whose custom integrations or build scripts link directly against that archive. Before upgrading, check for references to this path and instead install the platform's libpcap development package or provide a separate libpcap build. The libpcap headers under /opt/datadog-agent/embedded/include remain available.

• The com.datadoghq.remoteaction.agent Private Action Runner bundle (Preview) has been renamed to com.datadoghq.remoteaction.datadogagent. …

Agent

Prelude

Released on: 2026-09-24

• Please refer to the 7.83.3 tag on integrations-core for the list of changes on the Core Checks

Bug Fixes

• Fix missing log source configuration fields in public inventory metadata, including Windows Event Log queries, processing options, auto-multiline settings, and maximum message size.

Datadog Cluster Agent

Prelude

Released on: 2026-09-24 Pinned to datadog-agent v7.83.3: CHANGELOG.

Agent

Prelude

Released on: 2026-09-16

• Please refer to the 7.83.2 tag on integrations-core for the list of changes on the Core Checks

Enhancement Notes

• gpu: Constant metrics (gpu.device.total, gpu.memory.limit, gpu.core.limit, and gpu.memory.bar1.total) are reported on the cadence set by the new gpu.static_metrics_reporting_interval (15 seconds by default) to ensure accuracy when using weighted sums.
• Single Step Instrumentation's tracer config mechanisms (the ddTraceConfigs Targets field, remote-config policies, and the admission.datadoghq.com/apm-inject.tracer-configs pod annotation) now also accept OTEL_ prefixed environment variable names, in addition to the existing DD_ prefix. This allows configuring a tracer's native OpenTelemetry mode (e.g. OTEL_TRACES_EXPORTER, OTEL_EXPORTER_OTLP_ENDPOINT) through SSI.

Bug Fixes …

Agent

Prelude

Released on: 2026-09-09

• Please refer to the 7.83.1 tag on integrations-core for the list of changes on the Core Checks

Bug Fixes

• Fix bug which made fast network path test billed to customer
• Release the containerd view snapshot and lease taken for a container image SBOM scan even when the scan is cancelled or times out. The release ran on the scan's own context, so a scan that hit its deadline left the snapshot behind, and on a lazy snapshotter that snapshot holds the layer it materialised.

Other Notes

• The fleet installer daemon now reports the DDOT (OpenTelemetry Collector) process state as part of the agent state sent to Datadog, so DDOT version and configuration updates can be monitored. The state is read from the process manager when it supervises DDOT, and from systemd or the Windows service manager otherwise. It is also visible in the output of datadog-installer status.

Datadog Cluster Agent

Prelude

Released on: 2026-09-09 Pinned to datadog-agent v7.83.1: CHANGELOG.

Bug Fixes

• Fix Cluster Agent graceful shutdown to release the Kubernetes leader-election lock before exiting, allowing another replica to take over without waiting for the lease to expire.

Agent

Prelude

Released on: 2026-09-03

• Please refer to the 7.83.0 tag on integrations-core for the list of changes on the Core Checks

New Features

• Add a Data Security provider that schedules one-off database scan checks triggered through Remote Configuration. It is enabled when both data_security.enabled and shared_library_check.enabled are set, and currently targets PostgreSQL databases already monitored by the Agent (via the postgres check).

• Add k8s cluster receiver, k8s leader elector extension, and count connector to the DDOT (Datadog Distribution of OpenTelemetry Collector) default manifest, enabling collection of Kubernetes cluster-level metrics, leader election coordination for Kubernetes receivers, and count-based metric generation via the OpenTelemetry Collector pipeline.

• Add Helm rollback action

• Adds an Agent Data Plane (ADP) preflight mode, controlled by the new data_plane.preflight_mode setting (enabled by default).

  When data_plane.enabled has not been set at all, the Agent starts ADP once at startup for 90 seconds in an isolated configuration, sends a single throwaway metric through it, then stops it and reports any startup errors to Datadog as agent telemetry. This surfaces environment-specific ADP problems before ADP is enabled for real. …

Agent

Prelude

Released on: 2026-08-26

• Please refer to the 7.82.3 tag on integrations-core for the list of changes on the Core Checks

Enhancement Notes

• Agents are now built with Go 1.26.7.

Bug Fixes

• The Dynamic Instrumentation proxy in the trace-agent no longer drops debugger data when logs_enabled is left unset. Data is only dropped when logs_enabled (or the deprecated log_enabled) is explicitly set to false.
• On Windows, fixed an issue where upgrading the Agent without providing DDAGENTUSER_PASSWORD could lock out a domain Agent user account. The installer now leaves dd-procmgr-service, and the components it supervises, disabled until the Agent user password is provided again.

Datadog Cluster Agent

Prelude

Released on: 2026-08-26 Pinned to datadog-agent v7.82.3: CHANGELOG.

Agent

Prelude

Released on: 2026-08-19

• Please refer to the 7.82.2 tag on integrations-core for the list of changes on the Core Checks

New Features

• When infrastructure_mode: end_user_device is set, the logon_duration feature is now enabled automatically, so operators no longer need to set logon_duration.enabled: true separately. This setting can still be overridden explicitly in the configuration file if needed.

Enhancement Notes

• The Agent's embedded Python has been upgraded from 3.13.14 to 3.13.15
• Agents are now built with Go 1.26.6.

Bug Fixes

• APM: Raise the messagepack decoder allocation limit for the span meta_struct field to 10MiB, so large meta_struct entries (as written by LLM Observability) are no longer rejected by the package-wide 500,000 element limit. Other span fields keep the lower limit.
• Disable GPU parallel collection by default to avoid triggering NVML concurrency bugs.
• gpu: fix concurrent calls to NVML GetFieldValues API, that could cause missing NVLink metrics.

Other Notes

• gpu: GPU inventory payload and GPU tags are only emitted when GPU monitoring is enabled

Datadog Cluster Agent

Prelude

Released on: 2026-08-19 Pinned to datadog-agent v7.82.2: CHANGELOG.

Agent

Prelude

Released on: 2026-08-11

• Please refer to the 7.82.1 tag on integrations-core for the list of changes on the Core Checks

Bug Fixes

• Windows: Fixed an issue where an explicit DDAGENTUSER_KEEP_RIGHTS or DDAGENTUSER_NAME value passed as an install argument to a Fleet Automation-triggered Windows Agent install/upgrade could be silently overridden by a stale fallback value (respectively from the registry and from the running service account).
• Fix an issue where GPU monitoring could trigger a kernel panic on multi-GPU nodes with Hopper/Blackwell GPUs.

Datadog Cluster Agent

Prelude

Released on: 2026-08-11 Pinned to datadog-agent v7.82.1: CHANGELOG.

Agent

Known Issues

• GPU Monitoring can trigger a kernel panic on multi-GPU nodes with Hopper/Blackwell GPUs. The workaround is to disable parallel collection (gpu.parallel_collectors: false), downgrade to Agent v7.81.3 or upgrade to v7.82.1 when it becomes available.

Prelude

Released on: 2026-08-05

• Please refer to the 7.82.0 tag on integrations-core for the list of changes on the Core Checks

Upgrade Notes

• Automatic multi-line log detection (logs_config.auto_multi_line_detection) is now enabled by default. Multi-line log messages such as stack traces and JSON blobs are aggregated into a single log entry out of the box, instead of being split into separate entries. To restore the previous behavior, set logs_config.auto_multi_line_detection to false (or the environment variable DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION=false). …

Agent

Prelude

Released on: 2026-07-30

• Please refer to the 7.81.3 tag on integrations-core for the list of changes on the Core Checks

Bug Fixes

• Windows: Fixed an issue where the DDAGENTUSER_KEEP_RIGHTS opt-out was not preserved when the Agent was upgraded through Fleet Automation. Fleet-triggered upgrades uninstall and reinstall the Agent MSI as two separate steps, which cleared the stored opt-out before the reinstall could read it back, causing the SeDeny*LogonRight assignments on the Agent service account to be reapplied even when the customer had previously opted out with DDAGENTUSER_KEEP_RIGHTS=1. In-place MSI upgrades were not affected.
• Fixed an issue where Remote Configuration would sometimes attempt to process client requests that had already timed out.

Datadog Cluster Agent

Prelude

Released on: 2026-07-30 Pinned to datadog-agent v7.81.3: CHANGELOG.

Agent

Prelude

Released on: 2026-07-22

• Please refer to the 7.81.2 tag on integrations-core for the list of changes on the Core Checks

Upgrade Notes

• Metrics now use the Datadog v3 intake by default for Datadog destinations.

  Metric destinations configured with non-Datadog-looking URLs, such as custom additional_endpoints and reverse proxies, continue to use the v2 intake by default. To enable v3 for every destination, set use_v3_api.series.enabled: "true". To keep using v2 intake, set use_v3_api.series.enabled: "false" (global) or use_v3_api.series.endpoints: { "<url>": "false" } (per-endpoint).

Bug Fixes

• On macOS, opening the Datadog Agent GUI via the fallback launch method no longer steals focus from the application the user is currently working in.

Datadog Cluster Agent

Prelude

Released on: 2026-07-22 Pinned to datadog-agent v7.81.2: CHANGELOG.

Agent

Prelude

Released on: 2026-07-15

• Please refer to the 7.81.1 tag on integrations-core for the list of changes on the Core Checks

New Features

• Add a new reflector-based Kubernetes event collection path, enabled via event_collection_mode: watch.

Enhancement Notes

• Agents are now built with Go 1.26.5.

Datadog Cluster Agent

Prelude

Released on: 2026-07-15 Pinned to datadog-agent v7.81.1: CHANGELOG.

Agent

Prelude

Released on: 2026-07-08

• Please refer to the 7.81.0 tag on integrations-core for the list of changes on the Core Checks

Metrics are now forwarded to the new Datadog v3 API by default (/api/intake/metrics/v3/series). The v3 API payload format is more compact, reducing outbound bandwidth from Agents to Datadog.

If you configure additional_endpoints to forward to a non-Datadog endpoint, you will likely need to disable v3 for this endpoint. Otherwise you will see 404s. This can be done via:

use_v3_api:
  series:
    endpoints:
      "<additional_endpoint>": false

Example:

additional_endpoints:
  "https://non-datadog-endpoint":
    - apikey2

will need:

use_v3_api:
  series:
    endpoints:
      "https://non-datadog-endpoint": false

Metrics sent to Observability Pipelines Worker continue to use the v2 API by default.

To keep using v2 endpoint, set use_v3_api.series.enabled: "false" (global) or use_v3_api.series.endpoints: { "<url>": "false" } (per-endpoint; shown above).

Upgrade Notes

• The DDOT feature gate exporter.datadogexporter.metricremappingdisabled has been removed and replaced with exporter.datadogexporter.DisableAllMetricRemapping.

• Removed the agent status py subcommand (which wasn't officially supported) …