- [FEATURE] Add
kafka
monitoring recipe & tests, #113 @qqfr2507 - [FEATURE] Allow database name to be passed into postgres template, @miketheman
- [FEATURE] Add
relations
parameter to Postgres check config, #97 @miketheman - [FEATURE] Add
sock
parameter to MySQL check configuration, #105 @thisismana - [FEATURE] Add more parameters to the haproxy templte to collect status metrics, #103 @evan2645 & @miketheman
- [FEATURE]
datadog::mongo
recipe now installspymongo
and prerequisites, #81 @dwradcliffe - [FEATURE] Allow attribute control over whether to allow the local Agent to handle non-local traffic, #100 @coosh
- [FEATURE] Allow attribute control over whether the Chef Handler is activated, #95 @jedi4ever, @miketheman
- [FEATURE] Allow attribute control over whether Agent should be running, #94 @jedi4ever, @miketheman
- [FEATURE] Reintroduce attribute config for dogstatsd daemon, #90 @jedi4ever, @miketheman
- [FEATURE] Allow jmx template to accept arbitrary
key, value
statements, #93 @clofresh - [FEATURE] Allow cassandra/zookeeper templates to accept arbitrary
key, value
statements, @miketheman - [FEATURE] Add name param to varnish recipe, #86 @clofresh
- [FEATURE] Allow attribute-driven settings for web proxy, #82 @antonio-osorio
- [FEATURE] Allow override of Agent config for hostname via attribute, #76 @ryandjurovich
- [FEATURE] Allow for non-conf.d integrations to be set via attributes, #66 @babbottscott
- [FEATURE] added hdfs recipe and template, #77 @phlipper
- [FEATURE] added zookeeper recipe and template, #74 @phlipper
- [BUGFIX] Warn user when more than one
network
instance is defined, #98 @miketheman - [BUGFIX] Properly indent jmx template, #88 @flah00
- [BUGFIX] Handle unrecognized Python version strings in a better fashion, #79 #80 #84, @jtimberman, @schisamo, @miketheman
- [BUGFIX] Set gpgcheck to false for
yum
repo if it exists, #89 @alexism, #101 @nkts - [MISC] Inline doc for postgres recipe, #83 @timusg
- [FEATURE] added rabbitmq recipe and template, @miketheman
- [BUGFIX] memcache dependencies and template, #67 @elijahandrews
- [BUGFIX] redis python client check was not properly checking the default version, @remh
- [MISC] tailor 1.3.1 caught some cosmetic issue, @alq
- [FEATURE] Parameterize chef-handler-datadog Gem version, #60 @mfischer-zd
- [FEATURE] Allow control of
network.yaml
via attributes, #63 @JoeDeVries - [FEATURE] Use Python version from Ohai to determine packages to install, #65 @elijahandrews
- [BUGFIX] redisdb default port in template should be 6379, #59 @miketheman
- [BUGFIX] templates creating empty
tags
in config when unspecified for multiple integrations #61 @alq - [MISC] updated tests @elijahandrews, @miketheman
- [MISC] correct the riak integration example, @miketheman
- [MISC] updated CHANGELOG.md style, @miketheman
One of the dependencies of this cookbook is the apt
cookbook.
A change introduced in the apt
cookbook 2.0.0 release was a Chef 11-specific feature that would break on any Chef 10 system, so we considered adding a restriction in our metadata.rb
to anything below 2.0.0.
A fix has gone in to apt
2.1.0 that relaxes this condition, and plays well with both Chef 10 and 11. We recommend using this version, or higher.
- Fixed iis and rabbitmq template syntax - #58 @gregf
- Updated style/spacing in ActiveMQ template
- Updated test suite to validate cookbook & templates
- Updated chefignore to clean the built cookbook from containing cruft
-
BREAKING CHANGE: Moved all attributes into
datadog
namespace - #46 (#23, #26)Reasoning behind this was that originally we attempted to auto-detect many common attributes and deploy automatic monitoring for them. We found that since inclusion of the
datadog
cookbook early in the run list caused the compile phase to be populated with our defaults (mostlynil
), instead of the desired target, and namespacing of the attributes became necessary. -
NEW PROVIDER: Added a new
datadog_monitor
provider for integration useThe new provider is used in many pre-provided integration recipes, such as
datadog::apache
. This enables a run list to include this recipe, as well as populate a node attribute with the needed instance details to monitor the given service -
Updated dependencies in Gemfile, simplifies travis build - #34, #55
-
Much improved test system (chefspec, test-kitchen) - #35 & others
-
Tests against multiple versions of Chef - #18
-
Added language-specific recipes for installing
dogstatsd
- (#28) -
Added ability to control
dogstatsd
from agent config via attribute - #27 -
Placed the
dogstatsd
log file in/var/log/
instead of/tmp
-
Added attribute to configure dogstreams in
datadog.conf
- #37 -
Updated for
platform_family
semantics -
Added
node['datadog']['agent_version']
attribute -
(Handler Recipe) Better handling of EC2 instance ID for Handler - #44
-
Updated for agent 3.6.x logging syntax
-
Generated config file removes some whitespace - #56
-
Removed dependency on
yum::epel
, only usesyum
for therepository
recipe
- Quick fix for backporting test code to support upload in ruby 1.8.7
- Work-around for COOK-2171
- Fixed typo in jmx section
- Added support for postgres, redis & memcached
dd-agent
- updated to include more platformsdd-handler
- updated to leveragechef_gem
resource if available- Updated copyright for 2012
- Updated syntax for node attribute accessors
- Some syntax styling fixes
- Added agent logging configuration
- Removed extraneous dependencies
- Added automated testing suite
- Updated for CentOS dependencies
- Link to github repository.
dd-handler
- Corrects attribute name.
dd-agent
- Adds an explicit varnish attribute.
dd-agent
- Add varnish support.
dd-agent
- default to using instance IDs as hostnames when running dd-agent on EC2
dd-agent
- Full datadog.conf template using attributes (thanks @drewrothstein)
dd-agent
- Added support for Nagios PerfData and Graphite.
dd-agent
- Added support for RPM installs - Red Hat, CentOS, Scientific, Fedora
- Initial refactoring, including the
dd-agent
cookbook here - Adding chef-handler-datadog to report to the newsfeed
- Added ruby-dev dependency