|
2 | 2 | Release Notes
|
3 | 3 | =============
|
4 | 4 |
|
| 5 | +.. _Release Notes_7.65.0: |
| 6 | + |
| 7 | +7.65.0 |
| 8 | +====== |
| 9 | + |
| 10 | +.. _Release Notes_7.65.0_Prelude: |
| 11 | + |
| 12 | +Prelude |
| 13 | +------- |
| 14 | + |
| 15 | +Release on: 2025-05-06 |
| 16 | + |
| 17 | +- Please refer to the `7.65.0 tag on integrations-core <https://github.com/DataDog/integrations-core/blob/master/AGENT_CHANGELOG.md#datadog-agent-version-7650>`_ for the list of changes on the Core Checks |
| 18 | + |
| 19 | + |
| 20 | +.. _Release Notes_7.65.0_Upgrade Notes: |
| 21 | + |
| 22 | +Upgrade Notes |
| 23 | +------------- |
| 24 | + |
| 25 | +- Covers more gRPC status code values sent by tracer libraries |
| 26 | + |
| 27 | +- Aggregate APM stats payloads by gRPC code |
| 28 | + |
| 29 | + |
| 30 | +.. _Release Notes_7.65.0_New Features: |
| 31 | + |
| 32 | +New Features |
| 33 | +------------ |
| 34 | + |
| 35 | +- 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: |
| 36 | + |
| 37 | + `DD_APM_INSTRUMENTATION_ENABLED=iis DD_APM_INSTRUMENTATION_LIBRARIES=dotnet:3` |
| 38 | + |
| 39 | + Requires IIS 10.0 or later. |
| 40 | + For more information see [Single Step APM Instrumentation](https://docs.datadoghq.com/tracing/trace_collection/automatic_instrumentation/single-step-apm/). |
| 41 | + |
| 42 | +- APM: Added new OpenLineage event proxy endpoint. |
| 43 | + |
| 44 | +- A new implementation of auto multi-line detection for logs is now available. |
| 45 | + This new implementation is more flexible and powerful than the previous one. |
| 46 | + It now supports arbitrary timestamps, continuous matching, and more flexible configuration. |
| 47 | + It will be enabled automatically when ``logs_config.auto_multi_line_detection`` is set to ``true``. |
| 48 | + You can opt out of the new implementation by setting ``logs_config.force_auto_multi_line_detection_v1`` to ``true``. |
| 49 | + |
| 50 | +- APM: Container-based primary tags are now available by default. |
| 51 | + |
| 52 | + |
| 53 | +.. _Release Notes_7.65.0_Enhancement Notes: |
| 54 | + |
| 55 | +Enhancement Notes |
| 56 | +----------------- |
| 57 | + |
| 58 | +- Add a new host tag called ``orch_cluster_id`` that is set to the |
| 59 | + Kubernetes cluster ID generated by the cluster-agent. This is added only |
| 60 | + for the hosts that are part of a Kubernetes cluster. |
| 61 | + This tag is also used on every cluster-level resources like |
| 62 | + `kubernetes_state.*` metrics, kubernetes events, and orchestrator level |
| 63 | + resources. |
| 64 | + |
| 65 | +- Add ``admission.datadoghq.com/apm-inject.debug: "true"`` annotation to inject |
| 66 | + ``DD_APM_INSTRUMENTATION_DEBUG=true``, ``DD_TRACE_STARTUP_LOGS=true`` and |
| 67 | + ``DD_TRACE_DEBUG=true`` to an application container. |
| 68 | + This is useful for debugging Single Step Instrumentation or tracer issues |
| 69 | + in Kubernetes environments. |
| 70 | + |
| 71 | +- Add metrics origins for Sonatype Nexus, Silverstripe CMS and Anecdote integrations. |
| 72 | + |
| 73 | +- Add the `propagate_agent_tags setting`. When set to `true`, the tags from the Agent host are added to the check's tag for all instances. |
| 74 | + |
| 75 | +- Agents are now built with Go ``1.23.7``. |
| 76 | + |
| 77 | +- Agents are now built with Go ``1.23.8``. |
| 78 | + |
| 79 | +- Allow integrations to self-declare as HA Supported. |
| 80 | + |
| 81 | +- Improved trace context creation from Step Function execution context: |
| 82 | + - Now utilizes `State.RetryCount` and `Execution.RedriveCount` to generate parent IDs deterministically, preventing collisions with retry spans. |
| 83 | + - Supports multi-level trace merging, allowing an arbitrary number of Lambda and Step Function traces to be linked together while maintaining root context. |
| 84 | + |
| 85 | + This update brings feature parity with Node and Python Lambda layers in the Universal runtimes. |
| 86 | + |
| 87 | +- The hostname subcommand for the Agent now tries to reach out to the running Agent, |
| 88 | + and falls back to computing the hostname locally if the Agent is not running. |
| 89 | + You can use the `--local` option to force the local computation. |
| 90 | + |
| 91 | +- Cisco SD-WAN: improve memory usage. |
| 92 | + |
| 93 | +- Adds a `metadata_ip_resolution_from_hostname` config option to use |
| 94 | + hostname DNS resolution as the preferred method to compute the host IP address |
| 95 | + |
| 96 | +- Metrics are now sent over HTTP/2 when possible. A slight change to the |
| 97 | + connection handling to take full advantage of this means multiple requests |
| 98 | + can be in flight at any one time. This can be configured with the |
| 99 | + ``forwarder_max_concurrent_requests`` option, default is 10. |
| 100 | + |
| 101 | +- Added configurations ``network_path.collector.source_excludes`` and ``network_path.collector.dest_excludes``, which allow ignoring CIDR ranges in the Network Path collector. |
| 102 | + |
| 103 | +- Added support for querying the pod list through the API server. This feature, enabled by setting `kubeletUseApiServer` |
| 104 | + to `true`, allows the Agent to retrieve pod metadata directly from the API server instead of the kubelet. |
| 105 | + This resolves issues when direct access to the kubelet `/pods` endpoint is restricted. |
| 106 | + The agent will continue to query the kubelet for `/metrics` and `/stats/summary`. |
| 107 | + Must add `pods` to Agent cluster role. |
| 108 | + |
| 109 | +- Process checks now run in the core Agent by default on Linux. Process Agent will only run if needed for other configured features. |
| 110 | + |
| 111 | +- Include `container_instance_arn` in ECS Task payloads. |
| 112 | + |
| 113 | +- Include APIVersion and Kind to Kubernetes manifests. |
| 114 | + |
| 115 | +- The Python runtime is now loaded when the first check is loaded, rather than when the agent starts. |
| 116 | + This will eventually avoid having to load Python when no Python check is enabled. |
| 117 | + This change can be reverted by setting ``python_lazy_loading: false`` in your configuration. |
| 118 | + |
| 119 | +- When the API key can't be accessed in serverless, it is now logged as an error instead of debug. |
| 120 | + |
| 121 | +- Added FIPS compliance support for Lambda Extension GovCloud customers. The Lambda Extension now |
| 122 | + uses FIPS-enabled endpoints for AWS KMS and Secrets Manager when running in GovCloud regions. |
| 123 | + |
| 124 | +- APM: Return the correct content-type header when rejecting trace payloads. |
| 125 | + |
| 126 | +- APM: Expose an "obfuscation_version" value via the /info endpoint. Accept a new header "Datadog-Obfuscation-Version" for incoming stats payloads; if any non-zero value is set, the trace-agent will not attempt to obfuscate these payloads as they have already been obfuscated by the tracer. |
| 127 | + |
| 128 | +- Adds functionality to construct a DD span from `datadog.` attributes on an incoming span. By default, it checks for a span attribute starting with `datadog.`; if present, it uses this to compute the corresponding Datadog field (e.g., `datadog.service` is used to set `ddspan.Service`). This will override other sources for the same field (e.g., if both `datadog.service` and `service.name` are present, `datadog.service` is used). |
| 129 | + By default, if a field is missing, it will be recomputed (e.g., if there's no `datadog.env`, it will look for `env` in `deployment.environment`). However, if the config option `otlp_config.traces.ignore_missing_datadog_fields` is specified, the field will not be recomputed. This option allows users to explicitly specify blank fields if they desire (e.g., set `datadog.env = ""`). |
| 130 | + |
| 131 | + The following functionality is removed: if both `http.response.status_code` and `http.status_code` were present in the span attributes, the former was preferred. Similarly, `http.request.method` was preferred over `http.method`. In this release, the key encountered first is the one used. |
| 132 | + |
| 133 | + |
| 134 | +.. _Release Notes_7.65.0_Security Notes: |
| 135 | + |
| 136 | +Security Notes |
| 137 | +-------------- |
| 138 | + |
| 139 | +- The ``OPENSSL_CONF`` and ``OPENSSL_MODULES`` environment variables are now |
| 140 | + set when running the `datadog-fips-agent` in FIPS mode. This allows applications to use the |
| 141 | + OpenSSL configuration and modules configured with the Agent installation. |
| 142 | + |
| 143 | + |
| 144 | +.. _Release Notes_7.65.0_Bug Fixes: |
| 145 | + |
| 146 | +Bug Fixes |
| 147 | +--------- |
| 148 | + |
| 149 | +- Fixes bugs in the analyze-logs subcommand, and validates the logs config for invalid syntax. |
| 150 | + |
| 151 | +- Fixes a race condition introduced in PR #33521 around the PythonHome getting |
| 152 | + set in an init hook. |
| 153 | + |
| 154 | +- Fix the NVIDIA Jetson check to support parsing the ``tegrastats`` output |
| 155 | + when there are multiple Graphics Processing Clusters (GPCs). In that case, the metric |
| 156 | + ``nvidia.jetson.gpu.freq`` is emitted for each GPC and tagged with ``gpc:0``, ``gpc:1``, and so on. |
| 157 | + |
| 158 | +- Fixes issue where the CRI-O image status endpoint would be queried when `container_image.enabled` was set to `false`. |
| 159 | + |
| 160 | +- CWS: Fixed a bug that prevented more than one runtime security rule |
| 161 | + from being disabled, and caused incorrect policy information to |
| 162 | + be reported in ruleset loaded events. |
| 163 | + |
| 164 | +- Fixed a spinlock corruption in the Windows driver ddprocmon.sys that can cause system hangs and memory corruption when system-probe.exe is shutting down. |
| 165 | + |
| 166 | +- Fixes an issue where the system-probe would spuriously log the error ``netlink conntracker requires NET_ADMIN capability`` on the Fargate CNM preview. |
| 167 | + |
| 168 | +- Cisco SD-WAN: fix an issue that could lead to incorrect metrics tagging. |
| 169 | + |
| 170 | +- Fix the shebang of the `gstatus` binary to use the embedded Python environment. |
| 171 | + |
| 172 | +- APM: fix issue where a new span field for span events wasn't properly serialized when received in MessagePack format. |
| 173 | + |
| 174 | +- Environment variables that the kubelet collector receives and are |
| 175 | + not explicitly defined in plaintext will now be ignored. |
| 176 | + |
| 177 | + |
| 178 | +.. _Release Notes_7.65.0_Other Notes: |
| 179 | + |
| 180 | +Other Notes |
| 181 | +----------- |
| 182 | + |
| 183 | +- PHP support is enabled by default in the Cluster Agent |
| 184 | + |
| 185 | +- Metrics Origin entries for Infiniband and Celery integrations |
| 186 | + |
| 187 | +- Update OpenSSL from 3.4.0 to 3.4.1. |
| 188 | + |
| 189 | +- PHP support for Single Step Instrumentation is now installed by default. |
| 190 | + |
| 191 | +- Add metric origin for the Velero integration. |
| 192 | + |
| 193 | +- Adds the Datadog Installer service to the Agent MSI. The Datadog Installer service will start on boot but will exit |
| 194 | + unless the Remote Upgrades preview is enabled. |
| 195 | + |
| 196 | + |
5 | 197 | .. _Release Notes_7.64.3:
|
6 | 198 |
|
7 | 199 | 7.64.3
|
|
0 commit comments