-
Notifications
You must be signed in to change notification settings - Fork 812
Agent 4.0.0 for Windows
The Datadog Agent 4.0.0 is planned for release on 12-12-2013
This version contains various bug fixes and new features that are mostly impacting the following integrations:
If you are already using these integrations, please read the corresponding sections before upgrading to 4.0.0.
The Datadog Agent 4.0.0 also contains some new features and bug fixes, here is the rest of the Changelog..
The new version of the Agent includes a new in-house JMX Connector (JMXFetch: https://github.com/Datadog/jmxfetch) which is more efficient and more reliable than the previous connector (JMXTerm). The new connector will be limited to 100 metrics per instance. This limit was implemented as depending on your configuration, the check could collect tens of thousands of metrics which would cause high resources consumption (CPU/Memory/Network). To see if you are hitting that limit, you can simply read the info page after the agent has started.
- If you are hitting the limit, you can easily customize the metrics you want to collect by following this guide: http://docs.datadoghq.com/integrations/java/
- If you need to increase the limit of 100 metrics per instance, please get in touch with support@datadoghq.com
-
The previous version of the integration, bundled with dd-agent 3.x creates artificial hosts for each backend present in the HAProxy instance. A number of fellow customers have reported that this is confusing and we've updated the integration in the next major release of the agent (the technical details are here: https://github.com/DataDog/dd-agent/issues/617 ). The new version of the integration won't report the backend metrics as coming from these artificial hosts. There will have another tag to identify them (as explained in the github issue). It means that you will have to update any custom dashboard and metric alerts that you may have created to use the new tags.
-
By default, the new version of the agent will only collect metrics from the "aggregate" lines of HAProxy as those are the most useful. If you want to keep collecting metrics from every backend, you need to add the following flag in your haproxy.yaml file:
collect_aggregates_only: False```
(See https://github.com/DataDog/dd-agent/blob/master/conf.d/haproxy.yaml.example#L8)
## Other new features and bug fixes
### New features
- Add an option to forward every packet received to the Dogstatsd server: [How to use](https://github.com/DataDog/dd-agent/blob/master/datadog.conf.example#L85-L90)
- Collect EC2 tags at startup using IAM: [(fd404f2c7)](https://github.com/DataDog/dd-agent/commit/fd404f2c7e425cbb5be50e2b530f57ae135fee22)
- Add a CouchBase integration [#700](https://github.com/DataDog/dd-agent/pull/700) (Thanks [@jslatts](https://github.com/jslatts))
- Add the connections creation rate in the nginx check [#665](https://github.com/DataDog/dd-agent/pull/665) (Thanks [@dcrosta](https://github.com/dcrosta))
- Add the possibility to monitor more RabbitMQ Queues: [(51dd72b)](https://github.com/DataDog/dd-agent/commit/51dd72b9aae7007c2752147c1bdbc422935b1bd4)
- Add more metrics to the HAProxy integration regarding response codes: [(07f180ae)](https://github.com/DataDog/dd-agent/commit/07f180ae03e9cdbb5eccf3d5b26b8b8d36b2d74f)
### Bug fixes
- Fix a bug where the RabbitMQ check could fail [#742](https://github.com/DataDog/dd-agent/issues/742)
- Better performance and error handling of the MySQL check [#660](https://github.com/DataDog/dd-agent/pull/660) and [#671](https://github.com/DataDog/dd-agent/pull/671)
- Fix MongoDB integration which was broken on some versions of MongoDB [#677](https://github.com/DataDog/dd-agent/issues/677)