cookbook 'datadog', '= 3.4.1'
datadog
(82) Versions
3.4.1
-
-
4.21.0
-
4.20.0
-
4.19.0
-
4.18.0
-
4.17.0
-
4.16.0
-
4.15.0
-
4.14.0
-
4.13.0
-
4.12.0
-
4.11.1
-
4.11.0
-
4.10.0
-
4.9.0
-
4.8.0
-
4.7.2
-
4.7.1
-
4.7.0
-
4.6.0
-
4.5.0
-
4.4.0
-
4.3.0
-
4.2.1
-
4.2.0
-
4.1.1
-
4.1.0
-
4.0.1
-
4.0.0
-
3.5.1
-
3.5.0
-
3.4.1
-
3.4.0
-
3.3.0
-
3.2.0
-
3.1.0
-
3.0.0
-
2.20.1
-
2.20.0
-
2.19.0
-
2.18.0
-
2.17.0
-
2.16.1
-
2.16.0
-
2.15.0
-
2.14.1
-
2.14.0
-
2.13.0
-
2.12.0
-
2.11.0
-
2.10.1
-
2.10.0
-
2.9.1
-
2.9.0
-
2.8.1
-
2.8.0
-
2.7.0
-
2.6.0
-
2.5.0
-
2.4.0
-
2.3.0
-
2.2.0
-
2.1.0
-
2.0.0
-
1.2.0
-
1.1.1
-
1.1.0
-
1.0.1
-
1.0.0
-
0.1.4
-
0.1.3
-
0.1.2
-
0.1.1
-
0.1.0
-
0.0.12
-
0.0.11
-
0.0.10
-
0.0.9
-
0.0.8
-
0.0.4
-
0.0.3
-
0.0.2
-
0.0.1
Follow62
- 4.21.0
- 4.20.0
- 4.19.0
- 4.18.0
- 4.17.0
- 4.16.0
- 4.15.0
- 4.14.0
- 4.13.0
- 4.12.0
- 4.11.1
- 4.11.0
- 4.10.0
- 4.9.0
- 4.8.0
- 4.7.2
- 4.7.1
- 4.7.0
- 4.6.0
- 4.5.0
- 4.4.0
- 4.3.0
- 4.2.1
- 4.2.0
- 4.1.1
- 4.1.0
- 4.0.1
- 4.0.0
- 3.5.1
- 3.5.0
- 3.4.1
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.0
- 2.20.1
- 2.20.0
- 2.19.0
- 2.18.0
- 2.17.0
- 2.16.1
- 2.16.0
- 2.15.0
- 2.14.1
- 2.14.0
- 2.13.0
- 2.12.0
- 2.11.0
- 2.10.1
- 2.10.0
- 2.9.1
- 2.9.0
- 2.8.1
- 2.8.0
- 2.7.0
- 2.6.0
- 2.5.0
- 2.4.0
- 2.3.0
- 2.2.0
- 2.1.0
- 2.0.0
- 1.2.0
- 1.1.1
- 1.1.0
- 1.0.1
- 1.0.0
- 0.1.4
- 0.1.3
- 0.1.2
- 0.1.1
- 0.1.0
- 0.0.12
- 0.0.11
- 0.0.10
- 0.0.9
- 0.0.8
- 0.0.4
- 0.0.3
- 0.0.2
- 0.0.1
Installs/Configures datadog components
cookbook 'datadog', '= 3.4.1', :supermarket
knife supermarket install datadog
knife supermarket download datadog
Where to Find the Code
To submit issues and patches please visit https://github.com/DataDog/chef-datadog.
The code is licensed under the Apache License 2.0 (see LICENSE for details).
Datadog Cookbook
Chef recipes to deploy Datadog's components and configuration automatically.
This cookbook includes support for:
- Datadog Agent version 6.x
- Datadog Agent version 5.x
Log collection is available with Agent v6, please refer to the inline docs to enable it.
Note: This README may refer to features that are not released yet. Please check the README of the
git tag/the gem version you're using for your version's documentation
Requirements
- chef-client >= 12.7
If you need support for Chef < 12.7, please consider using a release 2.x of the cookbook.
See the CHANGELOG for more info.
Platforms
- Amazon Linux
- CentOS
- Debian
- RedHat (RHEL 8 requires chef >= 15)
- Scientific Linux
- Ubuntu
- Windows
- SUSE (requires chef >= 13.3)
Cookbooks
The following Opscode cookbooks are dependencies:
apt
chef_handler
yum
Version 7.1
or later of the apt
cookbook is needed to install the Agent on Debian 9 or later.
Chef support
Chef 13 users
- If you're using Chef 13 and chef_handler 1.x, you may have trouble using the
dd-handler recipe. The known workaround is to update your dependency to
chef_handler >= 2.1
.
Chef 14 and 15 users:
- In order to support Chef 12 and 13, the
datadog
cookbook has a dependency to thechef_handler
cookbook which is now shipped as a resource in Chef 14. Unfortunately, it will display a deprecation message to Chef 14 and 15 users.
Known Issues
Due to a critical bug in agent versions 6.14.0
and 6.14.1
for Windows, these versions have
been blacklisted in cookbook versions >=3.4.0
. >=2.20.0
.
PLEASE NOTE: chef-runs will fail on windows when updating to cookbook versions >=3.4.0
. >=2.20.0
if agent6
is set to true
and any of the following is true:
- any of the blacklisted Datadog Agent versions (6.14.0
or 6.14.1
) has been pinned in agent6_version
, or
- no Agent version is specified in the agent6_version
attribute (defaulting to 6.14.1
at the
time of this writing)
After uploading the latest datadog cookbook to your Chef Server and ensuring the cookbook has been
propagated to all nodes, upgrade the Agent version to 6.14.2
by setting the agent6_version
attribute.
If you are updating from 6.14.0 or 6.14.1 on Windows, we strongly recommend following these steps:
- Install the latest datadog cookbook on your Chef Server (
>=3.4.0
or>=2.20.0
) - Remove ALL prior versions of the datadog cookbook to ensure only the latest version of the cookbook
is available to your hosts. Please make sure to backup any modified or forked versions of the datadog
cookbook using
knife
orberks
if you need to reference them later. - Set the
agent6_version
attribute to6.14.2
PLEASE NOTE: It is important to ensure that your hosts ONLY use the latest version of the
datadog cookbook (>=3.4.0
or >=2.20.0
), before setting the agent6_version
attribute. This is a
precaution to ensure older versions of the datadog cookbook do not trigger the uninstall bug.
To learn more about this bug, please read here.
Recipes
default
Just a placeholder for now, when we have more shared components they will probably live there.
dd-agent
Installs the Datadog agent on the target system, sets the API key, and start the service to report on the local system metrics
Notes for Windows:
- Because of changes in the Windows Agent packaging and install in version 5.12.0, when upgrading the Agent from versions <= 5.10.1 to versions >= 5.12.0,
please set the
windows_agent_use_exe
attribute totrue
.
Once the upgrade is complete, you can leave the attribute to its default value (false
).
For more information on these Windows packaging changes, see the related docs on the dd-agent wiki.
dd-handler
Installs the chef-handler-datadog gem and invokes the handler at the end of a Chef run to report the details back to the newsfeed.
dogstatsd-ruby
Installs the language-specific libraries to interact with dogstatsd
.
For ruby, please use the datadog::dogstatsd-ruby
recipe.
For Python, please add a dependency on the poise-python
cookbook to your custom/wrapper cookbook, and use the following resource:
ruby
python_package 'dogstatsd-python' # assumes that python and pip are installed
For more advanced usage, please refer to the poise-python
cookbook documentation
ddtrace-ruby
Installs the language-specific libraries for application Traces (APM).
For ruby, please use the datadog::ddtrace-ruby
recipe.
For Python, please add a dependency on the poise-python
cookbook to your custom/wrapper cookbook, and use the following resource:
ruby
python_package 'ddtrace' # assumes that python and pip are installed
For more advanced usage, please refer to the poise-python
cookbook documentation
other
There are many other integration-specific recipes, that are meant to assist in deploying the correct agent configuration files and dependencies for a given integration.
Resources
datadog_monitor
The datadog_monitor
resource will help you to enable Agent integrations.
The default action :add
enables the integration by filling a configuration file for the integration with the values provided to the resource, setting the correct permissions on that file, and restarting the Agent.
The :remove
action disables an integration.
Syntax
datadog_monitor 'name' do init_config Hash # default value: {} instances Array # default value: [] logs Array # default value: [] use_integration_template true, false # default value: false action Symbol # defaults to :add if not specified end
Actions
-
:add
Default. Enable the integration. -
:remove
Use this action to disable the integration.
Properties
-
'name'
is the name of the Agent integration to configure and enable -
instances
are the fields used to fill values under theinstances
section in the integration configuration file. -
init_config
are the fields used to fill values under the theinit_config
section in the integration configuration file. -
logs
are the fields used to fill values under the thelogs
section in the integration configuration file. -
use_integration_template
: set totrue
(recommended) to use a default template that simply writes the values ofinstances
,init_config
andlogs
in YAML under their respective YAML keys. (defaults tofalse
for backward compatibility, will default totrue
in a future major version of the cookbook)
Example
This example enables the ElasticSearch integration by using the datadog_monitor
resource. It provides the instance configuration (in this case: the url to connect to ElasticSearch) and sets the use_integration_template
flag to use the default configuration template. Also, it notifies the service[datadog-agent]
resource in order to restart the Agent.
Note that the Agent installation needs to be earlier in the run list.
include_recipe 'datadog::dd-agent' datadog_monitor 'elastic' instances [{'url' => 'http://localhost:9200'}] use_integration_template true notifies :restart, 'service[datadog-agent]' if node['datadog']['agent_start'] end
See recipes/
for many examples using the datadog_monitor
resource.
datadog_integration
The datadog_integration
resource will help you to install specific versions
of Datadog integrations.
The default action :install
installs the integration on the node using the
agent integration install
command.
The :remove
action removes an integration from the node using the agent
command.
integration remove
Syntax
datadog_integration 'name' do version String # version to install for :install action. action Symbol # defaults to :install if not specified end
Actions
-
:install
Default. Installs an integration in the given version. -
:remove
Removes an integration.
Properties
-
'name'
is the name of the Agent integration to install, e.g.datadog-apache
-
version
is the version of the integration that you want to install. Only needed with the:install
action.
Example
This example installs version 1.11.0
of the ElasticSearch integration by
using the datadog_integration
resource.
Note that the Agent installation needs to be earlier in the run list.
include_recipe 'datadog::dd-agent' datadog_integration 'datadog-elastic' version '1.11.0' end
In order to get the available versions of the integrations, please refer to
their CHANGELOG.md
file in the integrations-core repository.
Note for Chef Windows users: as the datadog-agent binary available on the
node is used by this resource, the chef-client must have read access to the
datadog.yaml
file.
Usage
Agent v6
By default, this cookbook installs Agent v6, if you want to install Agent v5, please refer to the Agent v5 section below.
Attributes are available to have finer control over how you install Agent v6:
-
agent6_version
: allows you to pin the agent version (recommended). -
agent6_package_action
: defaults to'install'
, may be set to'upgrade'
to automatically upgrade to latest (not recommended, we recommend pinning to a version withagent6_version
and change that version to upgrade). -
agent6_aptrepo
: desired APT repo for the agent. Defaults tohttp://apt.datadoghq.com
-
agent6_aptrepo_dist
: desired distribution for the APT repo. Defaults tostable
-
agent6_yumrepo
: desired YUM repo for the agent. Defaults tohttps://yum.datadoghq.com/stable/6/x86_64/
Please review the attributes/default.rb file (at the version of the cookbook you use) for the list and usage of the attributes used by the cookbook.
For general information on the Datadog Agent v6, please refer to the datadog-agent repo.
Windows Agent v6 installation
Starting with version >= 6.11
, the Windows Agent v6 must be installed with datadog
cookbook version >= 2.18.0
.
This is due to the Agent v6 running with an unprivileged user on Windows
since 6.11. However, prior to 2.18.0, the datadog cookbook was enforcing
Administrators privileges to the Datadog Agent directories and files.
Extra configuration
Should you wish to add additional elements to the Agent v6 configuration file
(typically datadog.yaml
) that are not directly available
as attributes of the cookbook, you may use the node['datadog']['extra_config']
attribute. This attribute is a hash and will be marshaled into the configuration
file accordingly.
E.g.
default_attributes( 'datadog' => { 'extra_config' => { 'secret_backend_command' => '/sbin/local-secrets' } } )
or
default['datadog']['extra_config']['secret_backend_command'] = '/sbin/local-secrets'`
This example will set the field secret_backend_command
in the configuration
file datadog.yaml
.
For nested attributes, use object syntax:
E.g.
default['datadog']['extra_config']['logs_config'] = { 'use_port_443' => true }`
This example will set the field logs_config
in the configuration file datadog.yaml
.
Agent v5
Since 3.0.0
, the cookbook defaults installing Agent v6. You can still setup the Agent v5 by setting node['datadog']['agent6']
to false.
default_attributes( 'datadog' => { 'agent6' => false } )
Agent v5 transitions
Upgrade from Agent v5 to Agent v6
To upgrade from an already installed Agent v5 to Agent v6, you'll have to set the agent6_package_action
to install
and we recommend to pin to a specific version:
default_attributes( 'datadog' => { 'agent6' => true, 'agent6_package_action' => 'install', 'agent6_version' => { 'debian' => '1:6.14.2-1', 'rhel' => '6.14.2-1', 'windows' => '6.14.2' } } )
Note that there are Agent v6 counterparts to several well known Agent v5 attributes (code here)
Downgrade from an installed Agent v6 to an Agent v5
You will need to indicate that you want to setup an Agent v5 instead of v6, pin the Agent v5 version that you want to install and allow downgrade:
default_attributes( 'datadog' => { 'agent6' => false, 'agent_version' => '1:5.32.0-1', 'agent_allow_downgrade' => true } )
Instructions
- Add this cookbook to your Chef Server, either by installing with knife or by adding it to your Berksfile:
cookbook 'datadog', '~> 3.4.0'
- Add your API Key either:
- as a node attribute via an
environment
orrole
, or - as a node attribute by declaring it in another cookbook at a higher precedence level, or
- in the node
run_state
by settingnode.run_state['datadog']['api_key']
in another cookbook precedingdatadog
's recipes in the run_list. This approach has the benefit of not storing the credential in clear text on the Chef Server.
- as a node attribute via an
- Create an 'application key' for
chef_handler
here, and add it as a node attribute or in the run state, as in Step #2.
NB: if you're using the run state to store the api and app keys you need to set them at compile time before datadog::dd-handler
in the run list.
- Enable Agent integrations by including their recipes and configuration details in your role’s run-list and attributes.
Note that you can also create additional integrations recipes by using the
datadog_monitor
resource. - Associate the recipes with the desired
roles
, i.e. "role:chef-client" should contain "datadog::dd-handler" and a "role:base" should start the agent with "datadog::dd-agent". Here's an example role with both recipes plus the MongoDB integration enabled. ```ruby name 'example' description 'Example role using DataDog'
default_attributes(
'datadog' => {
'agent6' => true,
'api_key' => 'api_key',
'application_key' => 'app_key',
'agent6_version' => {
'debian' => '1:6.14.2-1',
'rhel' => '6.14.2-1',
'windows' => '6.14.2'
},
'mongo' => {
'instances' => [
{'host' => 'localhost', 'port' => '27017'}
]
}
}
)
run_list %w(
recipe[datadog::dd-agent]
recipe[datadog::dd-handler]
recipe[datadog::mongo]
)
``
agent6
NB: set theattribute to
falsein the
datadog` hash if you'd like to install Agent v5.
- Wait until
chef-client
runs on the target node (or trigger chef-client manually if you're impatient)
We are not making use of data_bags in this recipe at this time, as it is unlikely that you will have more than one API key and one application key.
For more deployment details, visit the Datadog Documentation site.
Chef 12
Depending of the Chef 12 version you're using, you will have to add some extra
dependency contraints.
Chef < 12.14
depends 'yum', '< 5.0'
Chef < 12.9
depends 'apt', '< 6.0.0' depends 'yum', '< 5.0'
AWS OpsWorks Chef Deployment
Add Chef Custom JSON:
json
{"datadog":{"agent6": true, "agent6_version": "1:6.14.2-1", "api_key": "<API_KEY>", "application_key": "<APP_KEY>"}}
Include the recipe in install-lifecycle recipe:
ruby
include_recipe 'datadog::dd-agent'
Changes
3.4.1 / 2019-11-15
- [FEATURE] Windows: add MSI max timeout knob. See #654 @truthbk
- [BUGFIX] Windows: add MSI max timeout knob. See #654 @olivielpeau
- [BUGFIX] Windows: use chef facilities instead of powershell to download 6.14 fix script. See #657 @truthbk
3.4.0 / 2019-11-11
- [FEATURE] Blacklist installation of 6.14.0 and 6.14.1. See #652 @truthbk
- [FEATURE] Run fix + sanity check script before agent uninstalls. See #652 @truthbk
3.3.0 / 2019-09-25
- [FEATURE] Add RHEL8/Fedora 28 support (needs Chef >= 15). See #641 @KSerrania
- [OPTIMIZE] Add support of the
cmd_port
andgui_port
fields in Agent config template. See #632 @iashwash @MCKrab - [OPTIMIZE] Add support of the
ssl_ca_cert
field in the vault template. See #624 @jschirle73 - [OPTIMIZE] Improve the README examples for the
extra_config
field. See #639 @nicholas-devlin
3.2.0 / 2019-07-25
- [FEATURE] Support the
extra_config
field in the system-probe recipe. See #635 @kevinconaway - [BUGFIX] Fix the support of SLES 15 by supporting recent versions of
gpg
while importing the GPG key. See #631 @KSerrania - [MISC] Allow custom prefix for Windows agent artifact. See #634 @truthbk
3.1.0 / 2019-07-10
- [FEATURE] Add support of the
system-probe
Agent. See #626 @shang-wang - [OPTIMIZE] Add support of the
extra_config
field in theprocess_config
section. See #628 @p-lambert
3.0.0 / 2019-06-12
Breaking changes
-
This cookbook only supports Chef 12.7+. It means that if you want to continue
to use this cookbook with a version of Chef
< 12.7
, you will have to use the datadog cookbook in a version< 3.0
. However, we recommend to switch to the3.x
version because there is no plan to update the2.x
branch with new features for now. -
Agent v6 is now installed by default. You can set
node['datadog']['agent6'] => false
to continue to use Agent v5. Please see the README for more details. - The
datadog_monitor
resource doesn't automatically restart the Agent anymore. Seerecipes/mongo.rb
for an example on how to restart the Agent afterdatadog_monitor
has been executed. See the README for more details on the resource. - A new attribute
node['datadog']['site']
will let you send the data to either the US or the EU site (this applies to the Datadog handler as well). Also,default['datadog']['url']
is now set tonil
. If not overriden in your cookbook, the Agent will pick which site to send data to based on these two attributes. - Drop support for chef-handler-datadog < 0.10.0, please use a more recent version.
- Add the
datadog_integration
resource to easily control installed integration, more info in the README. - Drop Agent v4 compatibility code.
Details
- [FEATURE] Ensure compatibility with Chef 14 & 15 (drop compatibility with Chef < 12.7). See #450 #597 @martinisoft @remeh
- [FEATURE] Agent 6 is now installed by default. See #594 @remeh
- [FEATURE] Support
jmx_custom_jars
option in Agent v5. See #595 @wolf31o2 - [FEATURE] Add
datadog_integration
resource to install integrations. See #600 @remeh - [FEATURE] Add support for
site
option. See #582 @remeh - [FEATURE] Add support of
max_detailed_exchanges
option for RabbitMQ. See #562 @asherf - [OPTIMIZE]
datadog_monitor
doesn't automatically restart the Agent. See #596 @someara @remeh - [OPTIMIZE] Remove deprecated attributes. See #613 @remeh
- [MISC] Remove recipes using
easy_install
. See #591 @stefanwb @remeh - [MISC] Drops Agent v4 compatibility code. See #599 @remeh
2.19.0 / 2019-05-21
2.18.0 / 2019-03-18
Note for Windows users: since Agent v6.11, datadog >= 2.18.0
is
necessary (see README)
- [FEATURE] Let the Windows installer set the permissions on Agent directories and files. #588 @remeh
- [BUGFIX] Use Upstart service manager for Ubuntu <15.04. See #551 @rposborne
- [MISC] Deprecation log for recipes using easy_install. See #585 @remeh
- [MISC] Add optional NGINX monitor attributes. See #564 @spencermpeterson
- [DOCS] Add an example for the
extra_config
field. See #586 @remeh
2.17.0 / 2019-03-01
- [FEATURE] Add support for SLES. See #505 @gmmeyer
- [FEATURE] Add
index_stats
parameter for ElasticSearch. See #568 @aymen-chetoui - [FEATURE] Add configuration flag for JMX service discovery in Agent 5. See #563 @wolf31o2
- [FEATURE] Add support for list of tags in v6 configuration file. See #557 @skarlupka
- [FEATURE] Add vault recipe. See #555 @skarlupka
- [FEATURE] Add
min_collection_interval
to mysql template. See #548 @mhebbar1 - [OPTIMIZE] Retry on failure when pulling the gpg key. See #561 @remicalixte
- [BUGFIX] Fix beans description in tomcat config template. See #583 @remeh
- [MISC] Switch to cookstyle. See #565 @jeffbyrnes
- [MISC] Bump requirement on
chef_handler
. See #396 @olivielpeau
2.16.1 / 2018-07-16
- [FEATURE] Add support for
no_proxy
Agent v6 option. See #549 @stonith - [MISC] Fix typo in documentation of
enable_logs_agent
option. See #544 @rsheyd
2.16.0 / 2018-05-14
- [FEATURE] Support data scrubber config fields for process agent. See #540 @moisesbotarro
- [MISC] Document
easy_install_package
removal from Chef 13+. See #533 @olivielpeau
2.15.0 / 2018-03-21
This release adds full support of Agent 6 on Windows.
- [FEATURE] Support passing arbitrary config options to Datadog handler. See #532 @olivielpeau
- [FEATURE] Update version logic for Agent 6 on Windows. See #530 @olivielpeau
- [FEATURE] Add support of APM options for Agent 6.0 and clean up beta workarounds. See #527 @olivielpeau
- [FEATURE] Set windows values for agent 6. See #525 @rlaveycal
- [OPTIMIZE] Update Agent 6 configuration for v6.0.0 stable and higher. See #531 @olivielpeau
- [OPTIMIZE] Update deprecated
logs_enabled
attribute. See #513 & #526 @eplanet - [OPTIMIZE] Allow configuring
tags_submission_retries
option on handler. See #508 @olivielpeau - [BUGFIX] Force
windows_service
to restart in order to cope with restart error. See #520 @stefanwb - [BUGFIX] Fix default
datadog.yaml
template for Windows. See #528 @olivielpeau
2.14.1 / 2018-03-05
- [BUGFIX] Fix service provider on Amazon Linux < 2.0. See #523 @olivielpeau
- [OPTIMIZE] Remove reference to old expired APT key, keep only newer key. See #522 @olivielpeau
2.14.0 / 2018-02-27
- [FEATURE] Enable log collection with chef. See #498 @NBParis
- [FEATURE] Support process agent configuration in datadog.yaml. See #511 @conorbranagan
- [FEATURE] Add recipe for WMI check. See #499 @mlcooper
- [FEATURE] Add updated metrics for Cassandra 2.x and 3.x. See #516 @olivielpeau
- [FEATURE] Update component for APT repo, and URL for YUM for Agent6. See #515 @olivielpeau
- [FEATURE] Consul: support self leader check and network latency checks. See #501 @azuretek
- [BUGFIX] RHEL/Amazon linux: add service provider hint for Agent6 + upstart. See #518 @olivielpeau
2.13.0 / 2017-12-01
- [FEATURE] Add support for Logs, See #490 @tmichelet
- [FEATURE] Add go-metro recipe, #484 @iancward
- [FEATURE] Add tokumx recipe, #486 @gswallow
- [FEATURE] Add couchbase recipe, #487 @gswallow
- [FEATURE] Add experimental support of Agent 6 beta RPMs, #493 @olivielpeau
- [FEATURE] Allow
disable_ssl_validation
in the apache conf, #480 @stolfi - [BUGFIX] Fix
warn_on_missing_keys
option of redis integration, #495 @iancward & @olivielpeau - [BUGFIX] Fix default log file directory on Windows, #492 @borgilb & @olivielpeau
- [BUGFIX] Add check to consul template for
tags
key, #479 @grogancolin
2.12.0 / 2017-09-28
- [FEATURE] Support of Agent 6 beta for debianoids, #472 @olivielpeau
- [FEATURE] Add
tag_families
option to RabbitMQ template, #437 & #460 @lefthand & @foobarto - [FEATURE] Bring elasticsearch template up-to-date, #445 & #462 @AlexBevan & @kylegoch
- [FEATURE] Add
additional_metrics
andcollections
to mongo template , #463 @otterdude97 - [OPTIMIZE] Explicitly set
gpgcheck
to true foryum_repository
, #458 @dafyddcrosby - [BUGFIX] Adding support for amazon linux based images with recent versions of ohai, #448 @frezbo
- [BUGFIX] Fix
ssl_verify
option of rabbitmq template, #474 @iancward - [DOCS] Fix missing array braces in supervisord example, #454 @benmanns
2.11.0 / 2017-09-21
- [FEATURE] Add configuration for the process-agent, #465 @conorbranagan
- [FEATURE] Add SNMP recipe, #436 @mlcooper
- [OPTIMIZE] Do not include
yum
recipe to avoid overwriting main yum config, #446 @olivielpeau - [BUGFIX] Avoid failures of agent
service
resource with frequent restarts on systemd, #469 @olivielpeau
2.10.1 / 2017-05-31
- [OPTIMIZE] Add compatibility with
windows
cookbook3.0
, #438 @olivielpeau
2.10.0 / 2017-05-08
- [FEATURE] Update nginx configuration template, #417 @iancward
- [FEATURE] Add service discovery attributes to
datadog.conf
, #420 @bflad - [FEATURE] Add Kubernetes recipe, #409 @xt99
- [FEATURE] Add SQLServer recipe, #425 @mlcooper
- [FEATURE] Add disk integration recipe, #430 @iancward
- [FEATURE] Add more options to Mongo & Elasticsearch templates, #424 @gkze
- [FEATURE] Allow disabling
apm_enabled
indatadog.conf
, #428 @ed-flanagan - [FEATURE] Let the trace-agent use its own default settings, #433 @olivielpeau
- [FEATURE] Allow specifying trace env, #435 @krasnoukhov
2.9.1 / 2017-03-28
2.9.0 / 2017-03-24
This release should be fully compatible with Chef 13.
Note for Windows users: Upgrading to Agent versions >= 5.12.0 should be done using the EXE installer
(see README)
- [FEATURE] Allow configuration of Traces settings in datadog.conf, #402 @mlcooper
- [FEATURE] Support upgrades to Windows Agents >= 5.12.0 (EXE installer option), #410 @olivielpeau
- [FEATURE] Add
send_policy_tags
option for handler, #398 @olivielpeau - [FEATURE] Add attribute to customize the gem server of the handler, #413 @dsalvador-dsalvador
- [OPTIMIZE] Rename
package[apt-transport-https]
resource for Chef 13 compatibility, #388 @bai - [OPTIMIZE] Guard new GPG key from always being downloaded, #404 @iancward
- [MISC] Loosen constraint on
chef_handler
cookbook version, #414 @olivielpeau - [MISC] Add constraint on
windows
cookbook version, #415 @olivielpeau
2.8.1 / 2017-02-03
- [BUGFIX] Fix agent version pinning on Windows, #400 @olivielpeau
2.8.0 / 2017-01-25
- [FEATURE] Add
ssl_verify
option to RabbitMQ template, #383 @iancward - [FEATURE] Add correct sudo commands to Postfix recipe, #384 @BrentOnRails & @degemer
- [FEATURE] Add support for
windows_service
integration, #387 @mlcooper - [FEATURE] Add attributes for package download retries, #390 @degemer
- [FEATURE] Add tags blacklist regex attribute for handler, #397 @ABrehm264 & @degemer
- [FEATURE] Defer evaluation of api and app keys and read from
run_state
, #395 @mfischer-zd
2.7.0 / 2016-11-15
- [FEATURE] Add
dd-agent
user todocker
group indocker
/docker_daemon
recipes, #364 @jvrplmlmn - [FEATURE] Add support for
system_swap
check, #372 @iancward - [FEATURE] Add ability to pin datadog-agent versions per platform, #368 @mlcooper
- [FEATURE] Add support for any config option in
datadog.conf
, #375 @degemer - [FEATURE] Trust new APT and RPM keys, #365 @olivielpeau
- [OPTIMIZE] Simplify
postgres.yaml
template, #380 @miketheman - [BUGFIX] Allow instances with no
tags
inpostfix
template, #374 @nyanshak
2.6.0 / 2016-09-20
- [FEATURE] Allow multiple enpoints/api_keys conf on Agent and handler, #317 @degemer
- [FEATURE] Add
kafka
template versioning, #340 @degemer - [FEATURE] Add
gunicorn
support, #355 @mlcooper - [FEATURE] Add attribute to allow agent downgrade, #359 @olivielpeau
- [OPTIMIZE] Fully disable dogstatsd when attribute is set to false/nil, #348 @ccannell67
- [OPTIMIZE] Use HTTPS for
yumrepo
when applicable, #351 @aknarts - [BUGFIX] Fix agent version test when version contains an epoch, #357 @olivielpeau
- [BUGFIX] Fix
datadog-agent-base
removal guard logic on rhellions, #358 @olivielpeau - [BUGFIX] Replace deprecated properties of
yum_repository
, #361 & #362 @historus & @olivielpeau
2.5.0 / 2016-08-08
- [FEATURE] Add support for
extra_packages
agent checks, #271 @tmichelet - [FEATURE] Add Windows support to
remove-dd-agent
recipe (Chef >= 12.6 only), #332 @raycrawford - [FEATURE] Make yum repo GPG key an attribute, #326 @iancward
- [FEATURE] Add support for
provider
option iniis
check, #324 @clmoreno - [FEATURE] Add support for tags in
etcd
check, #322 @stensonb - [FEATURE] Add
developer_mode
option todatadog.conf
, #315 @olivielpeau - [FEATURE] Add support for
win32_event_log
check, #314 @olivielpeau - [FEATURE] Add
dogstatsd_target
option todatadog.conf
, #313 @jcftang-r7 - [FEATURE] Add support for
custom_metrics
inpostgres
check, #284 @flah00 - [OPTIMIZE] Update windows support with many improvements, #334 @brentm5
- [OPTIMIZE] Pass the
hostname
attribute to the handler, #308 @gmmeyer - [MISC] Allow non-breaking updates of
chef_handler
, #291 @eherot
NOTE The strict version constraint on chef_handler
had been introduced because the 1.2
minor release
of chef_handler
broke compatibility with Chef 11. Chef 11 compatibility has been re-introduced in the 1.3
release, we recommend using that version or higher if you use Chef 11.
2.4.0 / 2016-05-04
- [FEATURE] Add support for
dns_check
, #294 @nickmarden - [FEATURE] Add support for
directory
check, #277 @kindlyseth - [BUGFIX] Template error in
postgres.yaml
, #300, #304 @miketheman
2.3.0 / 2016-04-25
- [FEATURE] Add support for
go_expvar
check, #298 @hartfordfive - [FEATURE] Allow a String or Hash when configuring Agent tags, #296 @martinisoft
- [FEATURE] Allow passing a
tag_prefix
to the handler, #285 @mstepniowski - [FEATURE] Allow Agent config to control service behavior, #280 @hydrant25 & @miketheman
- [FEATURE] Add
collect_function_metrics
topostgres
check, #278 @isaacdd - [FEATURE] Add logging configuration overrides, #273 @SupermanScott & @miketheman
- [FEATURE] Add
cassandra
template versions, #263 @yannmh @sethrosenblum & @miketheman - [FEATURE] Add
sites
options toiis
check, #261, @cobusbernard & @miketheman - [FEATURE] Add missing options to
rabbitmq
check, #232 @mattrobenolt & @miketheman - [FEATURE] Add Agent config option for
histogram_*
, #272, @SupermanScott - [FEATURE] Add support for
commandstats
in redis check, #266 @sethrosenblum - [FEATURE] Add support for
ssh_check
check, #262 @wk8 - [FEATURE] Add support for custom MySQL queries, #259 @wk8
- [FEATURE] Add PHP-FPM recipe, #253 @jridgewell
- [FEATURE] Allow
yum_repository
resource to receive proxy options, #251 @RedWhiteMiko - [FEATURE] Add Agent config option for
statsd_metric_namespace
, #250 @MiguelMoll - [FEATURE] Allow use of Agent
web_proxy
config for Handler, #208 @datwiz - [OPTIMIZE] Allow
tags
to benil
during Windows Agent install, #286 @rlaveycal - [OPTIMIZE] Apply
sensitive
filter to template renders, #274 @martinisoft - [DOCS] Correct
redisdb
example, #281 @iashwash - [DOCS] Correct
docker_daemon
example, #276 @dlackty - [MISC] Remove
knife.rb
file from repo, #299 @miketheman - [MISC] Convert Kitchen Test to ChefSpec test for
activemq
, #295 @miketheman - [MISC] Add Kitchen tests via CircleCI & kitchen-docker, @miketheman
- [MISC] Update Travis lint/spec tests to use ChefDK-supplied packages, @miketheman
2.2.0 / 2015-10-27
This release deserves a specific callout for a feature that has been finally
implemented and deserves a major round of applause to @EasyAsABC123,
@rlaveycal, @olivielpeau for their efforts in making Windows platform
support in this cookbook a reality.[FEATURE] Add support for
docker_daemon
check, #249 @kurochan[FEATURE] Add support for
solr
check, #246 @miketheman[FEATURE] Add support for
system_core
check, #243 @miketheman[FEATURE] Add support for
etcd
check, #235 @zshenker & @darron[FEATURE] Add RPM signature check, #225 @elafarge, #240 @miketheman
[FEATURE] Add timeout option to
elasticsearch
check, #223 @dominicchan[FEATURE] Add per-shard config toggles to
elasticsearch
check. Agent 5.5.0+, #221 @elafarge[FEATURE] Add per-check tagging to
datadog.conf
. Agent 5.5.0+, #220 @elafarge ref[FEATURE] Add port for
mysql
check, #217 @NathanielMichael[FEATURE] Add support for Windows, #210 @EasyAsABC123, @rlaveycal, @olivielpeau
[FEATURE] Add
skip_ssl_validation
toggle to the datadog config file, #209 @ABrehm264[FEATURE] Add support for
supervisord
check, #204 @DorianZaccaria[FEATURE] Add support for
pgbouncer
check, #198 @DorianZaccaria[FEATURE] Update options for
redisdb
check, #185 @opsline-radek, @miketheman (specs)[BUGFIX] Fix
kafka
templatetags
, #244 @LeoCavaille[BUGFIX] Fix
updated_by_last_action
value ofmonitor
provider, #229 @olivielpeau[BUGFIX] Make
zookeeper
checktimeout
optional, #227 @olivielpeau[OPTIMIZE] Detect virtual package prior to removal, #247 @dwradcliffe
[OPTIMIZE] Add source & issues URLs for Supermarket, #248 @jeffbyrnes
[OPTIMIZE] Skip
dd-handler
recipe inwhy-run
mode, #231 @olivielpeau[OPTIMIZE] Add
apt-transport-https
for deb-based repo install, #219 @darron[OPTIMIZE] Change rights on Agent configuration files, #218 @olivielpeau
[OPTIMIZE] Updates to
manage
LWRP, #212 @jmanero-r7[MISC] Add Rake task for cleanup, #216 @miketheman
[MISC] Update
guard
andGuardfile
, #215 @miketheman[MISC] Create ChefSpec matchers for spec testing, @miketheman
[MISC] Update
jmx
tests for accurate structure, @miketheman[MISC] Update libraries used in test suite, @miketheman
2.1.0 / 2015-04-20
- [FEATURE] Add support for
mesos
check, #200 @DorianZaccaria - [FEATURE] Add support for
docker
check, #197 @DorianZaccaria - [OPTIMIZE] Set compile_time when using chef_gem resource, #196 @miketheman
- [FEATURE] Add support for
ntp
check, #182 @chrissnell, @miketheman - [OPTIMIZE] Remove long-dead
debug_mode
and replace withlog_level
, #187 @remh - [FEATURE] Add support for
http
&tcp
monitoring check, #177 @mtougeron, #178 @chrissnell, @miketheman - [FEATURE] Add support for
fluentd
monitoring check, #191 @takus, #192 @miketheman - [FEATURE] Add support for process monitoring check, #190 @jpcallanta
- [FEATURE] Add configuration flags to elasticsearch template, #169 @chrissnell
- [FEATURE] Add configuration flag to control collection of EC2 tags from Agent, #159 @mirceal
- [FEATURE] Add Agent package attribute to control package provider action, #127, #147 @miketheman
- [OPTIMIZE] Use hkp keyserver URL on debianoids, #138 @khouse
- [BUGFIX] Use correct indentation for kafka recipe, correct values, add tests, #163, @donaldguy & @miketheman
- [BUGFIX] Use correct indentation for activemq recipe, correct param, add tests, #171 @SelerityMichael & @miketheman
- [FEATURE] Add support for bind_host parameter, #148 @jblancett
- [FEATURE] Add support for Fedora platform, #135 @juliandunn
- [FEATURE] Add recipe for package removal, #125 @bitmonk
- [FEATURE] Add support for custom emitters, #123 @arthurnn & @graemej
- [FEATURE] Add support for statsd forwarding in config file, #117 @ctrlok
- [BUGFIX] Simplify JMX configuration, #116 @miketheman
NOTE This has been broken for some time, and has had multiple attempts at fixing properly. The correct interface
has never been documented, and the implementation has always been left up to the reader. We have changed this to be
much simpler - instead of trying to account for any possible methods
- [BUGFIX] Correct cassandra template render flags, @miketheman
- [DOCS] Remove suggestion for python cookbook, as it is no longer needed. @miketheman
- [MISC] Updates to test suite for simplicity, deprecation warnings, dependencies @miketheman & @darron
2.0.0 / 2014-08-22
- BREAKING CHANGE: Datadog Agent 5.0.0 Release Edition
With the release of Datadog Agent 5.x, all Python dependencies are now bundled, and extensions for monitoring are no
longer needed. Integration-specific recipes no longer install any packages, so if you are using a version older than
5.x, you may have to install these yourself. This greatly simplifies deployment of all components for monitoring.
See commit b77582122f3db774a838f90907b421e544dd099c for the exact package resources that have been removed.
Affected recipes:
- hdfs
- memcache
- mongodb
- mysql
- postgres
-
redisdb
- BREAKING CHANGE: Removed chef_gem support for Chef versions pre 0.10.9.
We haven't supported this version of Chef in some time, so it's unlikely that you will be affected at all.
Just in case, please review what versions of Chef you have installed, and use an older version of this cookbook until
you can upgrade them.
- [OPTIMIZE] Update repository recipe to choose correct arch, @remh
- [OPTIMIZE] Remove conditional python dep for Ubuntu 11.04, @miketheman
- [OPTIMIZE] Remove extra
apt-get
call during Agent recipe run, @miketheman - [FEATURE] Add
kafka
monitoring recipe & tests, #113 @qqfr2507 - [FEATURE] Allow database name to be passed into postgres template, @miketheman
- [MISC] Many updates to testing suite. Faster style, better specs. @miketheman
1.2.0 / 2014-03-24
- [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
1.1.1 / 2013-10-17
- [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
1.1.0 / 2013-08-20
- [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
Dependency Note
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.
1.0.1 / 2013-05-14
- 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
1.0.0 / 2013-05-06
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 (mostly nil
), instead of the desired target, and namespacing of the attributes became necessary.
-
NEW PROVIDER: Added a new
datadog_monitor
provider for integration use
The 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
0.1.4 / 2013-04-25
- Quick fix for backporting test code to support upload in ruby 1.8.7
0.1.3 / 2013-01-27
- Work-around for COOK-2171
0.1.2 / 2012-10-15
- Fixed typo in jmx section
0.1.1 / 2012-09-18
- Added support for postgres, redis & memcached
-
dd-agent
- updated to include more platforms -
dd-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
0.0.12
- Updated for CentOS dependencies
0.0.11
- Link to github repository.
0.0.10
-
dd-handler
- Corrects attribute name.
0.0.9
-
dd-agent
- Adds an explicit varnish attribute.
0.0.8
-
dd-agent
- Add varnish support.
0.0.7
-
dd-agent
- default to using instance IDs as hostnames when running dd-agent on EC2
0.0.5
-
dd-agent
- Full datadog.conf template using attributes (thanks @drewrothstein)
0.0.4
-
dd-agent
- Added support for Nagios PerfData and Graphite.
0.0.3
-
dd-agent
- Added support for RPM installs - Red Hat, CentOS, Scientific, Fedora
0.0.2
- Initial refactoring, including the
dd-agent
cookbook here - Adding chef-handler-datadog to report to the newsfeed
- Added ruby-dev dependency
Collaborator Number Metric
3.4.1 passed this metric
Contributing File Metric
3.4.1 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file
Foodcritic Metric
3.4.1 passed this metric
No Binaries Metric
3.4.1 passed this metric
Testing File Metric
3.4.1 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file
Version Tag Metric
3.4.1 passed this metric
3.4.1 passed this metric
3.4.1 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file
Foodcritic Metric
3.4.1 passed this metric
No Binaries Metric
3.4.1 passed this metric
Testing File Metric
3.4.1 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file
Version Tag Metric
3.4.1 passed this metric
3.4.1 passed this metric
3.4.1 passed this metric
Testing File Metric
3.4.1 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file
Version Tag Metric
3.4.1 passed this metric
3.4.1 failed this metric
3.4.1 passed this metric