6.4.1 / 2018-08-01
Docker, Windows, Linux
Download links
Changes
Prelude
Release on: 2018-08-01
- Please refer to the 6.4.1 tag on integrations-core for the list of changes on the Core Checks.
- Please refer to the 6.4.1 tag on trace-agent for the list of changes on the Trace Agent.
- Please refer to the 6.4.1 tag on process-agent for the list of changes on the Process Agent.
New Features
- Create packaging for google cloud launcher integration.
- Add options to exclude specific payloads from being sent to Datadog.
In some environments, some of the gathered information is considered
too sensitive to be sent to Datadog (i.e. IP addresses in events or
service checks). This feature adds to option to exclude specific
payload types from being sent to the backend. - Collect container disk metrics less often in the docker check,
decreasing its effect on performance when enabled. - Autodiscovery now supports the %%hostname%% tag on the docker
listener This tag will resolve to the containers' hostname value if
present in the container inspect. It is useful if the container IP
is not available or erroneous. - Dogstatsd origin detection now supports container tagging for
Kubernetes clusters running containerd or cri-o, in addition to the
existing docker support - This release ships full support of Kubernetes 1.3+
- OpenShift ClusterResourceQuotas metrics are now collected by the
kube_apiserver check, under the openshift.clusterquota.* and
openshift.appliedclusterquota.* names. - Display the version for Python checks on the status page.
Enhancement Notes
- Adding DD_EXPVAR_PORT to the configuration environment variables.
- On Windows, Specifically log to both the log file and the event
viewer what initiated an agent shutdown. Also logs specific startup
errors to both the log file and event viewer. - The embedded Python has been bumped from 2.7.14 to 2.7.15
- Agent expvar metrics now have default values. Metrics like the
number of packets dropped by the agent or errors were previously not
reported until a first event occurred. This should make it easier to
use the expvar configurationagent_stats.yaml
. - Proxy settings can be configured through the environment variables
DD_PROXY_HTTP
,DD_PROXY_HTTPS
andDD_PROXY_NO_PROXY
. These
environment variables take precedence over theproxy
options
configured indatadog.yaml
, and behave exactly the same way as
these options. The standardHTTP_PROXY
,HTTPS_PROXY
and
NO_PROXY
are still honored but have known side effects on
integrations, for simplicity we recommended using the new
environment variables. For more information, please refer to our
proxy docs - Update to distribution metrics algorithm with improved accuracy
- Added ECS pause containers to the default docker exclusion list
- Adding logging for when the agent fails to detect the origin of a
packet in dogstatsd socket mode because of namespace issues. - The
skip_ssl_validation
configuration option can now be set
through the relatedDD_SKIP_SSL_VALIDATION
env var - The Agent will log failed healthchecks on query and during exit
- On Windows, provides installation parameter to set the cmd_port,
the port on which the agent command interface runs. To be used if
the default (5001) is already used by another program. - The kube_service tag is now collected on Kubernetes 1.3.x versions.
The matching uses a new logic. If it were to fail, reverting to the
previous logic is possible by setting the
kubernetes_map_services_on_ip option to true. - The Kubernetes event collection timeout is now configurable
- Logs Agent: Added SOCKS5 proxy support. Use
logs_config: socks5_proxy_address: fqdn.example.com:port
to set
the proxy. - The diagnose output is now sorted by the diagnosis name
- Adding the status of the DCA (If enabled) in the Agent status
command.
Upgrade Notes
- If the environment variables that can be used to configure a proxy
(DD_PROXY_HTTP
,DD_PROXY_HTTPS
,DD_PROXY_NO_PROXY
,
HTTP_PROXY
,HTTPS_PROXY
andNO_PROXY
) are present with an
empty value (e.g.HTTP_PROXY=""
), the Agent now uses this empty
value instead of ignoring it and using lower-precedence options.
Deprecation Notes
- Begin deprecating "Agent start" command. It is being replaced by
"run". The "start" command will continue to function, with a
deprecation notice
Security Issues
- 'app_key' value from the configuration is now redacted when
creating a flare with the agent.
Bug Fixes
- Fixes presence of invalid UTF-8 characters when docker log message
is greater than 16Kb - Fix a possible agent crash due to a race condition in the auto
discovery. - Fixed an issue with jmxfetch not being killed on agent exit.
- Errors logged before the agent initialized the log module are now
printed on STDERR instead of being silenced. - Detect and handle Docker messages without header.
- Fixes installation, packaging scripts for OpenSUSE LEAP and greater.
- In the event of being unable to lock the dd-agent user (eg. dd-agent
is an LDAP user) during installation, do not fail; print relevant
warning. - The leader election process is now restarted if the leader stops
leading. - Avoid Linux package installation failures when both the
initctl
andsystemctl
commands are present but upstart is used as the init
system
Other Notes
- The system information collected from gohai no longer includes
network information when the agent is running in a container since
the network information is for the the container and not the host
itself. - The ntp check now runs every 15 minutes by default to avoid
over-loading the NTP server pools - Added new command "run" to the agent. This command replaces the
"start" command, to reduce ambiguity with the service lifecycle
commands