Bot releases are hidden (Show)
Published by ogaca-dd over 3 years ago
Release on: 2021-03-02
forwarder_retry_queue_payloads_max_size
takes precedence over theforwarder_retry_queue_max_size
. Ifforwarder_retry_queue_max_size
is not set, you are not affected byforwarder_retry_queue_max_size
is set, butforwarder_retry_queue_payloads_max_size
is not set, the Agent usesforwarder_retry_queue_max_size * 2MB
as the value offorwarder_retry_queue_payloads_max_size
. It is recommended toforwarder_retry_queue_payloads_max_size
and removeforwarder_retry_queue_max_size
from the Agent configuration./etc/datadog-agent
and/tmp
as it prevents to inherit from Datadog Agent image. It wasAUTCONFIG_FROM_ENVIRONMENT=false
.stream-logs
to stream the logs beingno_proxy
setting for host metadata calls. Byno_proxy
use_proxy_for_cloud_metadata
to disable--flare
flag to jmx (list|collect)
commands to save checklogs_config.docker_container_use_file
.agent health
command6.25.1 ships the same features as 7.25.1 except for the Python versions it supports.
Please refer to the 7.25.1 changelog.
Release on: 2021-01-26
6.25.0 ships the same features as 7.25.0 except for the Python versions it supports.
Please refer to the 7.25.0 changelog.
Release on: 2021-01-14
--table
option to agent check
command to output results in1.14.12
libkrb5
Kerberos library to v1.18.3. This versionPublished by remeh almost 4 years ago
6.24.1 ships the same features as 7.24.1 except for the Python versions it supports.
Please refer to the 7.24.1 changelog.
Published by remeh almost 4 years ago
Fix a bug when parsing the current version of an integration that prevented
upgrading from an alpha or beta prerelease version.
During a domain installation in a child domain, the Windows installer can now use a user from a parent domain.
The Datadog Agent had a memory leak where some tags would be collected but
never cleaned up after their entities were removed from a Kubernetes
cluster due to their IDs not being recognized. This has now been fixed, and
all tags are garbage collected when their entities are removed.
Published by xlucas almost 4 years ago
Released on: 2020-12-10
Pinned to datadog-agent v7.24.0: CHANGELOG.
Add a new command 'datadog-cluster-agent health' to show the cluster
agent's health, similar to the already existing agent health
.
collect node information for the orchestrator explorer
Fill DatadogMetric AutoscalerReferences
field to ease usage/investigation of DatadogMetrics
The Cluster Agent can now collect stats from Cluster Level Check runners
to optimize its dispatching logic and rebalance the scheduled checks.
Allow providing custom tags to orchestrator resources.
Add new configuration parameter to allow 'GroupExec' permission on the secret-backend command.
The new parameter ('secret_backend_command_allow_group_exec_perm') is now enabled by default in the cluster-agent image.
Add resolve option to endpoint checks through new annotation ad.datadoghq.com/endpoints.resolve
. With ip
value, it allows endpoint checks to target static pods
Expose metrics for the cluster level checks advanced dispatching.
Fix 'readsecret.sh' permission in Cluster-Agent dockerfiles that removes other
permission.
Fix issue in Cluster Agent when using external metrics without DatadogMetrics where multiple HPAs using the same metricName + Labels would prevent all HPAs (except 1st one) to get values from Datadog
Ensure that leader election runs if orchestrator_explorer and leader_election are enabled.
Rename node role tag from "node_role" to "kube_node_role" in orchestrator_explorer collection.
Published by remeh almost 4 years ago
6.24.0 ships the same features as 7.24.0 except for the Python versions it supports.
Please refer to the 7.24.0 changelog.
Published by remeh almost 4 years ago
Release on: 2020-12-03
tcp_queue.rqueue.size
, tcp_queue.rqueue.min
, tcp_queue.rqueue.max
, tcp_queue.wqueue.size
, tcp_queue.wqueue.min
, tcp_queue.wqueue.max
) were generating too much data because there was one time series generated per TCP connection.tcp_queue.read_buffer_max_usage_pct
, tcp_queue.write_buffer_max_usage_pct
which are aggregating all the connections of a container.only_count_nb_context
option from the tcp_queue_length
check configuration has been removed and will be ignored from now on.Added new configuration flag,
system_probe_config.enable_conntrack_all_namespaces,
false by default. When set to true, this will allow system
probe to monitor conntrack entries (for NAT info) in all
namespaces that are peers of the root namespace.
Added JMX version and java runtime version to agent status page
kubernetes_pod_annotations_as_tags
(DD_KUBERNETES_POD_ANNOTATIONS_AS_TAGS
) now support regex wildcards:
'{"*":"<PREFIX>_%%annotation%%"}'
can be used as value to collect all pod annotations as tags.
kubernetes_node_labels_as_tags
(DD_KUBERNETES_NODE_LABELS_AS_TAGS
) now support regex wildcards:
'{"*":"<PREFIX>_%%label%%"}'
can be used as value to collect all node labels as tags.
Note: kubernetes_pod_labels_as_tags
(DD_KUBERNETES_POD_LABELS_AS_TAGS
) supports this already.
Listening for conntrack updates from all network namespaces
(system_probe_config.enable_conntrack_all_namespaces flag) is now turned
on by default
Expand pause container image filter
Adds misconfig check for hidepid=2 option on proc mount.
It's possible to ignore auto_conf.yaml
configuration files using ignore_autoconf
or DD_IGNORE_AUTOCONF
.
Example: DD_IGNORE_AUTOCONF="redisdb kubernetes_state"
APM: The trace-agent now automatically sets the GOMAXPROCS value in
Linux containers to match allocated CPU quota, as opposed to the matching
the entire node's quota.
APM: Lowered CPU usage when using analytics.
APM: Move UTF-8 validation from the span normalizer to the trace decoder, which reduces the number of times each distinct string will be validated to once, which is beneficial when the v0.5 trace format is used.
Add the config forwarder_retry_queue_payloads_max_size
which defines the
maximum size in bytes of all the payloads in the forwarder's retry queue.
When enabled, JMXFetch now logs to its own log file. Defaults to jmxfetch.log
in the default agent log directory, and can be configured with jmx_log_file
.
Added UDS support for JMXFetch
JMXFetch upgraded to 0.40.3
dogstatsd_mapper_profiles may now be defined as an environment variable DD_DOGSTATSD_MAPPER_PROFILES formatted as JSON
Add orchestrator explorer related section into DCA Status
Added byte count per log source and display it on the status page.
APM: refactored the SQL obfuscator to be significantly more efficient.
IO check: device_blacklist_re has been deprecated in favor of device_exclude_re.
The config options tracemalloc_whitelist and tracemalloc_blacklist have been
deprecated in favor of tracemalloc_include and tracemalloc_exclude.
APM: Fix a bug where non-float64 numeric values in apm_config.analyzed_spans
would disable this functionality.
Disable stack protector on system-probe to make it buildable on the environments which stack protector is enabled by default.
Some linux distributions like Alpine Linux enable stack protector by default which is not available on eBPF.
Fix a panic in containerd if retrieved ociSpec is nil
Fix random panic in Kubelet searchPodForContainerID due to concurrent modification of pod.Status.AllContainers
Add retries to Kubernetes host tags retrievals, minimize the chance of missing/changing host tags every 30mins
Fix rtloader build on strict posix environment, e.g. musl libc on Alpine Linux.
Allows system_probe to be enabled without enabling network performance monitoring.
Set network_config.enabled=false
in your system-probe.yaml
when running the system-probe without networks enabled.
Fixes truncated output for status of compliance checks in Security Agent.
Under some circumstances, the Agent would delete all tags for a workload if
they were collected from different sources, such as the kubelet and docker,
but deleted from only one of them. Now, the agent keeps track of tags per
collector correctly.
The utilities provided by the sysstat
package have been removed: the iostat
,
mpstat
, pidstat
, sar
, sadf
, cifsiostat
and nfsiostat-sysstat
binaries have been removed from the packaged Agent. This has no effect on the
behavior of the Agent and official integrations, but your custom checks may be
affected if they rely on these embedded binaries.
Activate security-agent service by default in the Linux packages of the Agent (RPM/DEB). The security-agent won't be started if the file /etc/datadog-agent/security-agent.yaml does not exist.
Published by CharlyF almost 4 years ago
Released on: 2020-10-21
Pinned to datadog-agent v7.23.1: CHANGELOG
7.23.0
, is"-"
would be loaded as a list). ThisPublished by bmikaili almost 4 years ago
Release on: 2020-10-21
ec2_prefer_imdsv2
parameter was ignored when fetching EC2 tags from the metadata endpoint. This fixes a misleading warning log that was logged even when ec2_prefer_imdsv2
was left disabled in the Agent configuration.Published by CharlyF about 4 years ago
Pinned to datadog-agent v7.23.0: CHANGELOG.
resolve
option to the endpoint checks (#5918).health
command (#6144).AutoscalerReferences
field to ease usage/investigation of DatadogMetrics (#6367).orchestrator_explorer
configuration to enable the cluster-id ConfigMap creation and Orchestrator Explorer instanciation (#6189).cluster-agent
commands to allow executing the readsecret.sh
script for the secret backend feature (#6445).Published by bmikaili about 4 years ago
Release on: 2020-10-06
encoding: utf-16-be
encoding: utf-16-le
other values are unsupported and ignored bykubelet
check error reporting in the output ofagent status
in the case where the agent cannot properly connectproject_id:
host tagproject:
host tag key, with thegce_send_project_id_tag
config setting.ec2_prefer_imdsv2
).ignore_resources
filter was matched.DD_ENV
, DD_SERVICE
and DD_VERSION
/opt/datadog-agent/embedded/bin
(example: python
, pip
) nowPublished by KSerrania about 4 years ago
Release on: 2020-09-17
Published by hush-hush about 4 years ago
Release on: 2020-08-25
Adds a gauge for system.mem.slab_reclaimable. This is part
of slab memory that might be reclaimed (i.e. caches). Datadog 7.x
adds SReclaimable memory, if
available on the system, to the system.mem.cached gauge by default. This
may lead to inconsistent metrics for clients migrating from Datadog
5.x, where system.mem.cached didn't
include SReclaimable memory. Adding a
gauge for system.mem.slab_reclaimable allows inverse
calculation to remove this value from the system.mem.cached gauge.
Expand GCR pause container image filter
Kubernetes events for pods, replicasets and deployments now have
tags that match the metrics metadata. Namely, pod_name, kube_deployment, kube_replicas_set.
Enabled the collection of the kubernetes resource requirements
(requests and limits) by bumping the agent-payload dep. and
collecting the resource requirements.
Implements resource fallbacks for complex compliance check
assertions.
Add system.cpu.num_cores metric with the number of CPU cores
(windows/linux)
compliance: Add support for Go custom compliance checks and
implement two for CIS Kubernetes
Make DSD Mapper also map metrics that already contain tags.
If the retrieval of the AWS EC2 instance ID or hostname fails,
previously-retrieved values are now sent, which should mitigate host
aliases flapping issues in-app.
Increase default timeout on AWS EC2 metadata endpoints, and make it
configurable with ec2_metadata_timeout
Add container incl./excl. lists support for ECS Fargate
(process-agent)
Adds support for a heap profile and cpu profile (of configurable
length) to be created and included in the flare.
Upgrade embedded Python 3 to 3.8.5. Link to Python 3.8 changelog:
https://docs.python.org/3/whatsnew/3.8.html
Note that the Python 2 version shipped in Agent v6 continues to be
version 2.7.18 (unchanged).
Upgrade pip to v20.1.1. Link to pip 20.1.1 changelog:
https://pip.pypa.io/en/stable/news/#id54
Upgrade pip-tools to v5.3.1. Link to pip-tools 5.3.1 changelog:
https://github.com/jazzband/pip-tools/blob/master/CHANGELOG.md
Introduces support for resolving pathFrom from in File and Audit
checks.
On Windows, always add the user to the required groups during
installation.
APM: A series of changes to internal algorithms were made which reduced
CPU usage between 20-40% based on throughput.
PYTHONPATH
variable is ignored correctly when