5.5.0 / 09-17-2015

Details

5.4.7...5.5.0

New integration(s)

Consul

Updated integrations

Agent Metrics
Amazon EC2
Btrfs
Couchbase
CouchDB
Disk
Docker
Elasticsearch
etcd
Google Compute Engine
HTTP Check
JMXFetch
Mesos
MongoDB
MySQL
Network
Nginx
PgBouncer
PostgreSQL
Process
RabbitMQ
Redis
Supervisor
System
Unix
Windows Event Viewer
WMI

Consul check

New Consul check.

Supported metrics:

Number of Consul Agents in the Cluter
consul.peers: tagged by consul_datacenter and mode (leader | follower)
Consul Catalog Nodes Up by Service
consul.catalog.nodes_up: tagged by consul_datacenter and consul_service_id
Consul Catalog Services Up by Node
consul.catalog.services_up: tagged by consul_datacenter and consul_node_id

Supported events:

consul.new_leader events when a leader change is detected.

See #1628

New Docker check

Datadog agent 5.5.0 introduces a new Docker check: 'docker_daemon'.

In terms of features, it adds:

Support for TLS connections to the daemon
New metrics:
- Network metrics
- Memory limits
- Container size (rootfs)
- Image size
Support for labels (convert them into tags). Off by default, uses a list of labels that should be converted.
Support for ECS tags: task name and task version

Backward incompatible changes:

docker.disk.size metric is renamed to docker.container.size_rw
Old optional metrics: https://github.com/DataDog/dd-agent/blob/5.4.x/checks.d/docker.py#L29-L38 Are not collected anymore
Old tags are not supported anymore (e.g. name instead of container_name)

As a consequence, the previous check 'Docker' is now deprecated and will not receive further support.

See #1908

Windows 64bit - Datadog Agent

The Datadog Agent is now available in a 64bit version on Windows.
For more information, please visit our Integrations/Agent page.

Flare on Windows

Datadog Agent flare feature makes easy to ship a tarball with logs and configurations to ease agent troubleshooting. Previously exclusive to Linux, it's now available on Windows.
For more information, please visit our wiki page.

[WARNING] JMX `host` tag issues & potential backward incompatibilities issues with service check monitors

JMX related checks -c.f. list below- were illegitimately submitting service checks tagged with the host value defined in the YAML configuration file. As it was overriding the agent hostname, with a value often equals to localhost, it was difficult to define and scope monitors based on these service checks.

The issue is addressed. JMX service checks have a new jmx_server tag which contains the YAML configuration host value so it does not replace the actual agent hostname in the host tag anymore.

Warning: these changes affect your JMX-service-checks related existing monitors scoped with the host tag. For more information, please get in touch with support@datadoghq.com

JMX related checks: ActiveMQ, Cassandra, JMX, Solr, Tomcat.

See #66

Deprecation notice

`datadog.conf` disk options

Disk options in datadog.conf file are being deprecated to promote the new Disk check introduced in the 5.4.0 release. It will be removed in a future version of the Datadog Agent.
Please consider conf.d/disk.yaml instead to configure it.

See #1758

Generic Mesosphere check

The previous generic Mesosphere check is deprecated, in favor of the Mesosphere master and slave specific checks introduced in the 5.4.0 release. It will be removed in a future version of the Datadog Agent.

See #1535

Previous Docker check

The previous Docker check is deprecated, in favor of the new one introduced in the 5.5.0 release. It will be removed in a future version of the Datadog Agent.