A module to:
Puppet >=2.7.x and <=4.2.x (we may work with newer versions, but untested). For detailed informations on compatibility, check the module page on the Puppet forge.
Install datadog_agent as a module in your Puppet master's module path.
puppet module install datadog-datadog_agent
You can keep using the datadog module but it becomes legacy with the release of datadog_agent 1.0.0. Upgrade to get new features, and use the puppet forge system which is way easier for maintenance.
- Delete the datadog module
rm -r /etc/puppet/modules/datadog - Install the new module from the puppet forge
puppet module install datadog-datadog_agent - Update your manifests with the new module class, basically replace
datadogbydatadog_agent
include 'datadog_agent::integrations::elasticsearch'
Once the datadog_agent module is installed on your master, there's a tiny bit of configuration
that needs to be done.
-
Update the default class parameters with your API key
-
Specify the module on any nodes you wish to install the DataDog Agent.
include datadog_agent
Or assign this module using the Puppet style Parameterized class: class { 'datadog_agent': api_key => "yourkey", }
On your Puppet master, enable reporting:
class { 'datadog_agent':
api_key => "yourkey",
puppet_run_reports => true,
}
To support reporting, your Puppet master needs to have the dogapi gem installed, to do that either run the puppet agent on your master with this configuration or install it manually with gem.
Please note if on Puppet Enterprise or POSS (ie. >=3.7.0) there is a soft dependency for reporting on the puppetserver_gem module. Install with puppet module install puppetlabs-puppetserver_gem - installing manually with gem will not work.
Also note that we have made the gem provider configurable, so you can set it to puppetserver_gem (already set by default) if on PE/POSS (>=3.7.0) or gem if on older versions of puppet
-
Include any other integrations you want the agent to use, e.g.
include 'datadog_agent::integrations::mongo'
To enable reporting of changes to the Datadog timeline, enable the report processor on your Puppet master, and enable reporting for your clients. The clients will send a run report after each check-in back to the master.
Make sure you enable the puppet_run_reports option to true in the node
configuration manifest for your master.
class { "datadog-agent":
api_key => "<your_api_key>",
puppet_run_reports => true
# ...
}In your Puppet master /etc/puppet/puppet.conf, add these configuration options:
[main]
# No need to modify this section
# ...
[master]
# Enable reporting to datadog
reports=datadog_reports
# If you use other reports already, just add datadog_reports at the end
# reports=store,log,datadog_reports
# ...
[agent]
# ...
pluginsync=true
report=trueAnd on all of your Puppet client nodes add:
[agent]
# ...
report=trueIf you get
err: Could not send report:
Error 400 on SERVER: Could not autoload datadog_reports:
Class Datadog_reports is already defined in Puppet::Reports
Make sure reports=datadog_reports is defined in [master], not [main].
This is the minimal set of modifications to get started. These files assume puppet 2.7.x or higher.
[master]
report = true
reports = datadog_reports
pluginsync = true
[agent]
report = true
pluginsync = true
node "default" {
class { "datadog_agent":
api_key => "INSERT YOU API KEY HERE",
}
}
node "puppetmaster" {
class { "datadog_agent":
api_key => "INSERT YOUR API KEY HERE",
puppet_run_reports => true
}
}
import "nodes.pp"
sudo /etc/init.d/puppetmaster restart
sudo puppet agent --onetime --no-daemonize --no-splay --verbose
You should see something like:
info: Retrieving plugin
info: Caching catalog for alq-linux.dev.datadoghq.com
info: Applying configuration version '1333470114'
notice: Finished catalog run in 0.81 seconds
Go to the Setup page and you should see this
If you click on the tile, you may reconfirm it's been automatically installed.
Search for "Puppet" in the Stream and you should see something like this:
This is a specific setup, you can use https://gist.github.com/LeoCavaille/cd412c7a9ff5caec462f to set it up.
The datadog agent configuration file will be recreated from the template every puppet run. If you need to tag your nodes, add an array entry in hiera
datadog_agent::local_tags
- 'keyname:value'
- 'anotherkey:%{factname}'
Here are some of the other variables that be set in the datadog_agent class to control settings in the agent:
| variable name | description |
|---|---|
| collect_ec2_tags | Set this to yes to have an instance's custom EC2 tags used as agent tags |
| collect_instance_metadata | Set this to yes to have an instance's EC2 metadata used as agent tags |
| dd_url | datadog intake server URL. You are unlikely to need to change this |
| host | overrides the node's hostname |
| local_tags | an array of key:value strings that will be set as tags for the node |
| non_local_traffic | set this to allow other nodes to relay their traffic through this one |
If you need to connect to the internet through a proxy, you can set proxy_host, proxy_port, proxy_user and proxy_password.
git clone git@github.com:DataDog/puppet-datadog-agent.git
cd puppet-datadog-agent
bundle install
rake lint # Check puppet manifests with puppet-lint / Run puppet-lint
rake spec # Run spec tests in a clean fixtures directory
rake syntax # Syntax check Puppet manifests and templates
rake syntax:manifests # Syntax check Puppet manifests
rake syntax:templates # Syntax check Puppet templates
pip install pre-commit
pre-commit install
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request