Chef cookbook for Datadog Agent & Integrations
Ruby HTML Shell
Permalink
Failed to load latest commit information.
attributes Allow to specify trace env (#435) May 5, 2017
libraries [run_state] Improve CI, documentation and backwards compatibility Jan 24, 2017
providers [rubocop] Fix rubocop offenses (#389) Jan 3, 2017
recipes [windows] Add compatibility with windows cookbook 3.0 (#438) May 31, 2017
resources [Integrations] Add logic to install extra_packages agent checks (#271) Aug 4, 2016
spec Add Recipe for disk integration (#430) May 3, 2017
templates/default Allow to specify trace env (#435) May 5, 2017
test/integration [dd-handler] Loosen constraint on `chef_handler` dep (#414) Mar 22, 2017
.gitignore ignore some local dev env files [ci skip] Jan 27, 2015
.kitchen.docker.yml [ci] Fix CI (#432) May 2, 2017
.kitchen.yml Update windows support to be much better (#334) Aug 5, 2016
.rspec update spec testing options and location Jan 16, 2015
.rubocop.yml [run_state] Improve CI, documentation and backwards compatibility Jan 24, 2017
.travis.yml [ci] Fix CI (#432) May 2, 2017
Berksfile use current supermarket API endpoint Oct 10, 2016
CHANGELOG.md πŸ’Ž chef-datadog, 2.10.1 May 31, 2017
LICENSE A new year happened again! (#350) Sep 9, 2016
README.md [windows] Add option to support EXE Agent installer (#410) Mar 23, 2017
Rakefile [dd-handler] Loosen constraint on `chef_handler` dep (#414) Mar 22, 2017
chefignore ignore test subdir in chefignore Aug 20, 2013
circle.yml Add CircleCI parallel kitchen testing Apr 15, 2016
metadata.rb πŸ’Ž chef-datadog, 2.10.1 May 31, 2017

README.md

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).

Chef cookbook Build Status Circle CI Coverage Status GitHub forks GitHub stars Build Status

Datadog Cookbook

Chef recipes to deploy Datadog's components and configuration automatically.

NB: 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 >= 10.14

Platforms

  • Amazon Linux
  • CentOS
  • Debian
  • RedHat
  • Scientific Linux
  • Ubuntu
  • Windows (requires chef >= 12.0)

Cookbooks

The following Opscode cookbooks are dependencies:

  • apt
  • chef_handler
  • windows
  • yum

Note for Chef 11 users: please use these additional dependency version contraints for compatibility with Chef 11:

cookbook 'apt', '< 4.0'
cookbook 'chef_handler', '< 2.0'
cookbook 'windows', '< 2.0'
cookbook 'yum', '~> 3.0'

(in Berkshelf/Librarian format)

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:

  • With Chef >= 12.6 and the windows cookbook >= 1.39.0, Agent upgrades are known to fail. For Chef>=12.6 users on Windows, we recommend pinning the windows cookbook to a lower version (~> 1.38.0 for instance).

    If that's not an option, a known workaround is to use the remove-dd-agent recipe (since the 2.5.0 version of the present cookbook) to uninstall the Agent prior to any Agent upgrade.

  • 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 to true.

    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-(python|ruby)

Installs the language-specific libraries to interact with dogstatsd.

ddtrace-(python|ruby)

Installs the language-specific libraries for application Traces (APM).

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.

Usage

  1. Add this cookbook to your Chef Server, either by installing with knife or by adding it to your Berksfile:
cookbook 'datadog', '~> 2.7.0'
  1. Add your API Key either:
  • as a node attribute via an environment or role, or
  • as a node attribute by declaring it in another cookbook at a higher precedence level, or
  • in the node run_state by setting node.run_state['datadog']['api_key'] in another cookbook preceding datadog's recipes in the run_list. This approach has the benefit of not storing the credential in clear text on the Chef Server.
  1. 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.

  2. 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:

name 'example'
description 'Example role using DataDog'

default_attributes(
  'datadog' => {
    'api_key' => 'api_key',
    'application_key' => 'app_key'
  }
)

run_list %w(
  recipe[datadog::dd-agent]
  recipe[datadog::dd-handler]
)
  1. 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.