Bot releases are hidden (Show)
Published by arbll almost 6 years ago
Please note that a critical bug has been identified in this release that would prevent the kubernetes integration from collecting kubelet metrics.
The severity of the issue has led us to remove the packages for the
affected platform (Docker) and to make the latest
tag point to the 6.7.0
release.
If you have upgraded to this version of the containerized agent we recommend you downgrade to 6.7.0
.
Release on: 2018-12-13
Please refer to the 6.8.0 tag on integrations-core for the list of changes on the Core Checks.
Please refer to the 6.8.0 tag on trace-agent for the list of changes on the Trace Agent.
Please refer to the 6.8.0 tag on process-agent for the list of changes on the Process Agent.
The Datadog Agent now automatically look for the container short image name to set the default value for the log source and service.
The source is especially important as it triggers the automatic configuration of your platform with integration pipeline and facets.
The Datadog Agent autodiscovery can still be used to override the default source and service with pod annotations or container labels.
Enable docker config provider if docker.sock exists
The new command datadog-agent config
prints the runtime config of the
agent.
Adds eBPF-based network collection component called network-tracer.
Add diagnosis to the agent for connectivity to the cluster agent
datadog-agent integration install
command prevents a user from downgrading an integration
to a version older than the one shipped by default in the agent.
Adding kerberos support with libkrb5.
datadog-agent integration install
command moves configuration files present in
the data
directory of the wheel upon successful installation
Adding a default location on Windows for the file storing pointers to make sure we never lose nor duplicate any logs
Add an option to the agent check
command to run the check n times
Set service and source to the docker short image name when container_collect_all flag
is enabled and no label or annotation is defined
Docker: the datadog/dogstatsd image now ships a healthcheck
Improved consistency of the ECS and Fargate tagging
Improve logging when python checks use invalid types for tags
Added a region
tag to Fargate containers, indicating the AWS region
they run in
Adds system.cpu.interrupt, and system.mem.committed, system.mem.paged,
system.mem.nonpaged, system.mem.cached metrics on Windows
Add permissions.log
file to the flare archive.
Add an agent go-routine dump to the flare as reported
by the built-in pprof runtime profiling interface.
The agent can now expose its healthcheck on a dedicated http port.
The Kubernetes daemonset uses this by defaut, on port 5555.
It's possible now to have different poll intervals for
each autodiscovery configuration providers
Improve Windows Event parsing. Event.EventData.Data fields are parsed as one JSON object. Event.EventData.Binary field
is parsed to its string value
Rename the Windows Event "#text" field to "value". This fixes the facet
creation of those fields
Add a status.log
and a config-check.log
with a basic message in the flare
if the agent is not running or is unreachable.
Added support for wildcards to DD_KUBERNETES_POD_LABELS_AS_TAGS
. For example,
DD_KUBERNETES_POD_LABELS_AS_TAGS='{"*":"kube_%%label%%"}'
will all pod labels as
tags to your metrics with tags names prefixed by kube_
.
Configure error log when failing to run docker inspect to read as debug instead, as this log is duplicated by the tagger.
Fix a bug where datadog-agent integration
users could not test the
--in-toto
flag due to a filesystem permission issue.
The cluster agent client init now fails as expected if the
cluster agent URL is not valid
Print correct error when the datadog-agent integration
command fails after installing an integration
Fix build failure on 32bit armv7
Fix a bug with Docker logging driver where logs would not be tailed after a log
rotation when the option --log-opt max-file=1
was set.
Display the correct timezone name in the status page.
On Windows, the agent now properly computes the location of ProgramData for
configuration files instead of using hardcoded values
JMXFetch upgraded to 0.23.0. See https://github.com/DataDog/jmxfetch/releases/tag/0.23.0
On linux, use the cgo dns resolver instead of the golang one. The will make
the agent use glibc to resolve hostnames and should give more predictable
results.
Published by arbll almost 6 years ago
This release only ships changes to the trace-agent.
This release focuses on simplifying Trace Search configuration. APM Events can now be configured at the tracer level. Tracers will get updated in the near future to expose this option.
Published by hush-hush almost 6 years ago
Release on: 2018-10-25
clusterchecks
config providerdatadog-agent integration install
command will now check fordatadog-checks-base
shipped with the agent. In--in-toto
flag to datadog-agent integration
command to--verbose
flag to datadog-agent integration
command tosite
, that allows setting the Datadogdd_url
is stillsite
.host:
tagecs_agent_container_name
option or theDD_ECS_AGENT_CONTAINER_NAME
envvar for autodetection.empty_default_hostname
min_collection_interval
option, askubelet_wait_on_missing_container
option to handle hostsdatadog-agent integration
command will not pull any of thelogs
is invaliddatadog-agent integration
command with TUF enabled.datadog-agent integration
command, we replace the PyPI index withdatadog-agent integration
command to prevent accidentalPublished by truthbk about 6 years ago
Docker, Windows, Linux, MacOS
Release on: 2018-09-20
Published by truthbk about 6 years ago
Docker, Windows, Linux
logs_config.container_collect_all
or the environment variable DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL
are set to true.Published by truthbk about 6 years ago
Please note that a critical bug identified in this release affecting container log collection when the container_collect_all
was set, would lead to an agent deadlock. The severity of the issue has led us to remove the packages for the affected platforms (Linux and Docker). If you have upgraded to this version, on Linux or Docker we recommend you downgrade to 6.4.2
.
docker
and kubelet
listeners will retry on error, to support starting the agent before your container runtime (host install)cluster_name
option is available. It will be added as a suffix to the host alias detected from the kubelet in order to make these aliases unique across different clusters.docker_labels_as_tags
option to extract custom tagscluster_name
tag shortershort_image
and container_id
tagslogs_config.dd_url
, logs_config.dd_port
and logs_config.dev_mode_no_ssl
are deprecated and will be unavailable soon, use the new parameters logs_config.logs_dd_url
and logs_config.logs_no_ssl
instead.dd_url
is set to app.datadoghq.eu
, the infra Agent also sends data to versioned endpoints (similar to app.datadoghq.com
)collect_gce_tags
configuration option.hosts
is now available in the ntp check configuration file toAutodiscovery now enforces the ac_exclude and ac_include filtering options for all listeners. Please double-check your exclusion patterns before upgrading and add inclusion patterns if some autodiscovered containers match these.
The introduction of multiple runners for checks implies check instances may now run concurrently. This should help the agent make better use of resources, in particular it will help prevent or reduce the side-effects of slow checks delaying the execution of all other checks.
The change will affect custom checks not enforcing thread safety as they may, depending on the schedule, access unsynchronized structures concurrently with the corresponding data race ensuing. If you wish to run checks in a fully sequential fashion, you may set the check_runners option in your datadog.yaml config or via the DD_CHECK_RUNNERS to 1. Also, please feel free to reach out to us if you need more information or help with the new multiple runner/concurrency model.
For more details please read the technical note in the datadog.yaml.
Prometheus custom checks are now limited to 2000 metrics by default to provide users control over the maximum number of custom metrics sent in the case of configuration errors or input changes. This limit can be changed with the max_returned_metrics
option in the check configuration.
aggregator/ServiceCheckFlushed)
to aggregator/ServiceCheckFlushed
check
subcommand using the -l
flag was not setting the log level of python integrations.Published by olivielpeau about 6 years ago
Docker, Windows, Linux
Release on: 2018-08-13
Published by hush-hush about 6 years ago
Docker, Windows, Linux
Release on: 2018-08-01
agent_stats.yaml
.DD_PROXY_HTTP
, DD_PROXY_HTTPS
and DD_PROXY_NO_PROXY
. Theseproxy
optionsdatadog.yaml
, and behave exactly the same way asHTTP_PROXY
, HTTPS_PROXY
andNO_PROXY
are still honored but have known side effects onskip_ssl_validation
configuration option can now be setDD_SKIP_SSL_VALIDATION
env varlogs_config: socks5_proxy_address: fqdn.example.com:port
to setDD_PROXY_HTTP
, DD_PROXY_HTTPS
, DD_PROXY_NO_PROXY
,HTTP_PROXY
, HTTPS_PROXY
and NO_PROXY
) are present with anHTTP_PROXY=""
), the Agent now uses this emptyinitctl
systemctl
commands are present but upstart is used as the initPublished by arbll over 6 years ago
Docker, Windows, Linux
Release on: 2018-07-16
Please refer to the 6.3.3 tag on integrations-core for the list of changes on the Core Checks.
Please refer to the 6.3.3 tag on trace-agent for the list of changes on the Trace Agent.
Please refer to the 6.3.3 tag on process-agent for the list of changes on the Process Agent.
Fix the IO check behavior on unix based on 'iostat' tool:
Kubernetes API Server's polling frequency is now customisable.
Use as expected the configuration value of kubernetes_metadata_tag_update_freq,
introduce a kubernetes_apiserver_client_timeout configuration option.
Fix a bug that led the agent to panic in some cases if
the log_level
configuration option was set to error
.
Published by arbll over 6 years ago
Docker, Windows, Linux
Released on: 2018-07-04
Docker, Windows, Linux
Release on: 2018-06-27
Please refer to the 6.3.1 tag on integrations-core for the list of changes on the Core Checks.
Please refer to the 6.3.1 tag on trace-agent for the list of changes on the Trace Agent.
Please refer to the 6.3.1 tag on process-agent for the list of changes on the Process Agent.
Fixes panic when the agent receives an unsupported pattern in a log processing rule
Fixes problem in 6.3.0 in which agent wouldn't start on Windows
Server 2008r2.
Provide the actual JMX check name as check_name
in configurations
provided to JMXFetch via the agent API. This addresses a regression
in 6.3.0 that broke the instance:
tag.
Due to the nature of the regression, and the fix, this will cause
churn on the tag potentially affecting dashboards and monitors.
Published by arbll over 6 years ago
Docker, Windows, Linux
Release on: 2018-06-20
proxy
*_PROXY
environment variables, and thehttps://
scheme, the Agenthttp://
scheme before upgrading to v6.3+. This hasproxy
configuration you may use.C:
drive only./lib
is not a symlink to /usr/lib
.hostname -f
on unix-based systems before tryingos.Hostname()
. This flag is turned off by default for 6.3 and willcustom_jar_paths
and/ortools_jar_path
options are set, by using a semicolon as the pathdd-agent
user with no/sbin/nologin
or /usr/sbin/nologin
). The packagesdd-agent
user if it alreadyMetrics
toMetric Samples
to reflect that the number represents the number ofPublished by hush-hush over 6 years ago
2018-05-23
project:
andnumeric_project_id:
tags) and GCP instance attributes.Published by olivielpeau over 6 years ago
Docker, Windows, Linux, macOS
system.mem.commit_limit
and system.mem.committed_as
datadog-agent status
and to the GUI.bind_host
config option.Published by olivielpeau over 6 years ago
Docker, Windows, Linux, macOS
Our development staff observed that a local, unprivileged user had the ability to make an HTTP request to the /agent/check-config endpoint on the agent process that listens on localhost. This request would result in the local-users' ability to read Agent integration configurations. This issue was patched by enforcing authentication via a session token. Please upgrade your agent accordingly.
/agent/check-config
endpoint has been patched to enforce authentication of the caller via a bearer session token.Published by olivielpeau over 6 years ago
Docker, Windows, Linux, macOS
Published by arbll over 6 years ago
Docker, Windows, Linux, Mac OSX
Published by arbll over 6 years ago
Docker, Windows, Linux
Published by arbll over 6 years ago
Docker, Windows, Linux, Mac OSX
Add Agent Version to flare form
Add the DD_CHECK_RUNNERS environment variable binding
Add the status command to the DCA.
Docker check: ignore the new exec_die event type by default
Extract the swarm_namespace tag for docker swarm containers, in addition
to the already present swarm_service tag.
Allow configuration of the enabled-state of process, logs, and apm to be
specified on the installation command line for Windows.
Add a jmx_use_cgroup_memory_limit option to set jmxfetch to use cgroup
memory limits when calculating its heap size. It is enabled by default
in the docker image.
Add option to extract kubernetes pod annotations as tags, similar to labels
Added an environment variable DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL
to enable logs tailing on all containers.
Adding the 'bind_host' option to configure the interface to bind by dogstatsd and JMX.
Support setting tags as a YAML array in the logs agent integration configuration
Fix docker memory metrics parsing from cgroup files
Fix docker.mem.in_use metric computation
When using the import script, change the group owner of configuration files to the dd-agent user.
Fix a false positive in the collector-queue healthcheck
The old docker_daemon check is now properly converted in the "import" command by default
Docker check: fix event filtering for exec events
Improve docker monitoring when the system is under a very high load. The agent
might still temporarily miss a healthcheck, but will be able to run already
scheduled checks, and recover once the spike ends
Fixes the container startup on Fargate, where we tried and remove the same
file twice, failing hard (stopping) on the second attempt.
Fix flare failing on zipping individual components
Fixed an issue where the import script would put an empty histogram aggregates and percentiles in datadog.yaml if they didn't exist in datadog.conf.
Fix the build for platforms not supporting Gohai.
Fixes flaw where Windows Performance counters were not properly initialized
on non EN-US versions of windows
Menu in system tray reports wrong version (6.0.0) for all versions of Agent. This fixes the system tray menu to report the correct version.
Fixing clear passwords in "config-check.log" when sending a flare.
Allow network proxy settings set on the Windows installation command
line to be set in the registry, where they'll be translated to the
configuration
Accept now short names for docker image in logs configuration file and added to the possibilty to filter containers by image name with Kubernetes.
Fixes an issue that would prevent the agent from stopping when it was tailing logs
of a container that had no logs.
fixes an issue with wildcard tailing of logs files on windows
Allow Linux package uninstallation to proceed without errors even on platforms
that aren't supported by the Agent
Fixes agent to run on Server "Core" versions
Changes default precision of pdh-based counters from int to float. Fixes bug where fidelity of some counters is quite low, especially counters with values between 0 and 1.
Adds back the removed system.mem.usable metric for Agents running on Windows.
Avoid multiple initializations of the tagger subsystem
Normalize support of nested config options defined with env vars.
Make the check-rate command more visible when running "check` to get a list of metrics.
Published by truthbk over 6 years ago
Docker, Windows, Linux, Mac OSX