Release on: 2023-06-05
peer.service to trace stats exported by the Agent.span.kind value.Cluster Agent: User config, cluster Agent deployment and node Agent daemonset manifests are now added to the flare archive, when the Cluster Agent is deployed with Helm (version 3.23.0+).
Datadog Agent running as a systemd service can optionally read environment variables from a text file <span class="title-ref">/etc/datadog-agent/environment</span> containing newline-separated variable assignments. See https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Environment
Add ability to filter kubernetes containers based on autodiscovery annotation. Containers in a pod can now be omitted by setting <span class="title-ref">ad.datadoghq.com/<container_name>.exclude</span> as an annotation on the pod. Logs can now be ommitted by setting <span class="title-ref">ad.datadoghq.com/<container_name>.logs_exclude</span> as an annotation on the pod.
Added support for custom resource definitions metrics: <span class="title-ref">crd.count</span> and <span class="title-ref">crd.condition</span>.
sbom.cached_keys: Number of cache keys stored in memorysbom.cache_disk_size: Total size, in bytes, of the database as reported by BoltDB.sbom.cached_objects_size: Total size, in bytes, of cached SBOM objects on disk. Limited by sbom.custom_cache_max_disk_size.sbom.cache_hits_total: Total number of cache hits.sbom.cache_misses_total: Total number of cache misses.sbom.cache_evicts_total: Total number of cache evicts.Added <span class="title-ref">DD_ENV</span> to the SBOMPayload in the SBOM check.
Added <span class="title-ref">kubernetes_state.hpa.status_target_metric</span> and <span class="title-ref">kubernetes_state.deployment.replicas_ready</span> metrics part of the <span class="title-ref">kubernetes_state_core</span> check.
Add support for emitting resources on metrics from tags in the format dd.internal.resource:type,name.
APM: Dynamic instrumentation logs and snapshots can now be shipped to multiple Datadog logs intakes.
Adds support for OpenTelemetry span links to the Trace Agent OTLP endpoint when converting OTLP spans (span links are added as metadata to the converted span).
Agents are now built with Go 1.19.9.
Make Podman DB path configurable for rootless environment. Now we can set $HOME/.local/share/containers/storage/libpod/bolt_state.db.
Add ownership information for containers to the container-lifecycle check.
Add Pod exit timestamp to container-lifecycle check.
The Agent now uses the <span class="title-ref">ec2_metadata_timeout</span> value when fetching EC2 instance tags with AWS SDK. The Agent fetches instance tags when <span class="title-ref">collect_ec2_tags</span> is set to <span class="title-ref">true</span>.
Upgraded JMXFetch to 0.47.8 which has improvements aimed to help large metric collections drop fewer payloads.
Kubernetes State Metrics Core: Adds collection of Kubernetes APIServices metrics
Add support for URLs with the <span class="title-ref">http|https</span> scheme in the <span class="title-ref">dd_url</span> or <span class="title-ref">logs_dd_url</span> parameters when configuring endpoints. Also automatically detects SSL needs, based on the scheme when it is present.
[pkg/netflow] Add NetFlow Exporter to NDM Metadata.
SUSE RPMs are now built with RPM 4.14.3 and have SHA256 digest headers.
observability_pipelines_worker can now be used in place of the vector config options.
Add an option and an annotation to skip kube_service tags on Kubernetes pods.
When the selector of a service matches a pod and that pod is ready, its metrics are decorated with a kube_service tag.
When the readiness of a pod flips, so does the kube_service tag. This could create visual artifacts (spikes when the tag flips) on dashboards where the queries are missing .fill(null).
If many services target a pod, the total number of tags attached to its metrics might exceed a limit that causes the whole metric to be discarded.
In order to mitigate these two issues, it’s now possible to set the kubernetes_ad_tags_disabled parameter to kube_config to globally remove the kube_service tags on all pods:: kubernetes_ad_tags_disabled
It’s also possible to add a tags.datadoghq.com/disable: kube_service annotation on only the pods for which we want to remove the kube_service tag.
Note that kube_service is the only tag that can be removed via this parameter and this annotation.
Support OTel semconv 1.17.0 in OTLP ingest endpoint.
When otlp_config.metrics.histograms.send_aggregation_metrics is set to true, the OTLP ingest pipeline will now send min and max metrics for delta OTLP Histograms and OTLP Exponential Histograms when available, in addition to count and sum metrics.
The deprecated option otlp_config.metrics.histograms.send_count_sum_metrics now also sends min and max metrics when available.
OTLP: Use minimum and maximum values from cumulative OTLP Histograms. Values are used only when we can assume they are from the last time window or otherwise to clamp estimates.
The OTLP ingest endpoint now supports the same settings and protocol as the OpenTelemetry Collector OTLP receiver v0.75.0.
Secrets with <span class="title-ref">ENC[]</span> notation are now supported for proxy setting from environment variables. For more information you can refer to our [Secrets Management](https://docs.datadoghq.com/agent/guide/secrets-management/) and [Agent Proxy Configuration](https://docs.datadoghq.com/agent/proxy/) documentations.
[corechecks/snmp] Adds ability to send constant metrics in SNMP profiles.
[corechecks/snmp] Adds ability to map metric tag value to string in SNMP profiles.
[corechecks/snmp] Add support to format bytes into ip_address
ADDLOCAL=NPM and REMOVE=NPM, no longer controls the install state of NPM components. The NPM components are now always installed, but will only run when enabled in the agent configuration. The Windows Installer NPM feature option still exists for backwards compatability purposes, but has no effect.otlp_config.metrics.histograms.send_count_sum_metrics in favor of otlp_config.metrics.histograms.send_aggregation_metrics.pkg/forwarderdevice tag on the system.disk group of metrics.device.ip to exporter.ipprometheus.io/scrape: true, the Agent used to schedule one openmetrics check per container in the pod unless a datadog.prometheusScrape.additionalConfigs[].autodiscovery.kubernetes_container_names list was defined, which restricted the potential container targets. The Agent is now able to leverage the prometheus.io/port annotation to schedule an openmetrics check only on the container of the pod that declares that port in its spec.Fetched April 3, 2026