# Source: https://docs.datadoghq.com/agent/supported_platforms/chef.md

---
title: Chef
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Agent > Supported Platforms > Chef
---

# Chef

The Datadog Chef cookbook automates the installation and configuration of the Datadog Agent across supported Linux and Windows platforms. The cookbook is compatible with `chef-client >= 12.7`, and supports Windows and Linux platforms. For full attribute references, recipes, usage examples, and integration configuration patterns, see the Advanced configurations section.

The Datadog Chef recipes are used to deploy Datadog's components and configuration automatically. The cookbook includes support for:

- Datadog Agent v7.x (default)
- Datadog Agent v6.x
- Datadog Agent v5.x

**Note**: This page may discuss features that are not available for your selected version. Check the README of the git tag or gem version for your version's documentation.

## Prerequisites{% #prerequisites %}

The Datadog Chef cookbook is compatible with `chef-client` >= 12.7. If you need support for Chef < 12.7, use a [release 2.x of the cookbook](https://github.com/DataDog/chef-datadog/releases/tag/v2.18.0). See the [CHANGELOG](https://github.com/DataDog/chef-datadog/blob/master/CHANGELOG.md) for more info.

#### Platforms{% #platforms %}

The following platforms are supported:

- AlmaLinux (requires Chef 16 >= 16.10.8 or Chef >= 17.0.69)
- Amazon Linux
- CentOS
- Debian
- RedHat (RHEL 8 requires Chef >= 15)
- Rocky (requires Chef 16 >= 16.17.4 or Chef >= 17.1.35)
- Scientific Linux
- Ubuntu
- Windows
- SUSE (requires Chef >= 13.3)

#### Cookbooks{% #cookbooks %}

The following Opscode cookbooks are dependencies:

- `apt`
- `chef_handler`
- `yum`

**Note**: `apt` cookbook v7.1+ is needed to install the Agent on Debian 9+.

#### Chef{% #chef %}

**Chef 13 users**: With 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.

## Setup{% #setup %}

### Installation{% #installation %}

To install the Datadog Agent with Chef, follow the [in-app flow in Fleet Automation](https://app.datadoghq.com/fleet/install-agent/latest?platform=chef) setup guide for Berkshelf or Knife. This setup guide allows you to select observability features, and generates the necessary attributes and commands for your environment.

These setup steps are also listed below:

````text
    # Berksfile
    cookbook 'datadog', '~> 4.0'
    ```
    ```shell
    # Knife
    knife cookbook site install datadog
    ```
2. Set the [Datadog-specific attributes](#datadog-attributes) in a role, environment, or another recipe:
    ```text
    node.default['datadog']['api_key'] = "<YOUR_DD_API_KEY>"
    node.default['datadog']['application_key'] = "<YOUR_DD_APP_KEY>"
    ```
3. Upload the updated cookbook to your Chef server:
    ```shell
    berks upload
    # or
    knife cookbook upload datadog
    ```
4. After uploading, add the cookbook to your node's `run_list` or `role`:
    ```text
    "run_list": [
      "recipe[datadog::dd-agent]"
    ]
    ```
5. Wait for the next scheduled `chef-client` run or trigger it manually.


### Datadog attributes

The following methods are available for adding your [Datadog API and application keys][4]:

* As node attributes with an `environment` or `role`.
* As node attributes by declaring the keys in another cookbook at a higher precedence level.
* 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 does not store the credential in clear text on the Chef Server.

**Note**: When using the run state to store your API and application keys, set them at compile time before `datadog::dd-handler` in the run list.

## Advanced configurations

To add additional elements to the Agent configuration file (typically `datadog.yaml`) that are not directly available as attributes of the cookbook, use the `node['datadog']['extra_config']` attribute. This is a hash attribute, which is marshaled into the configuration file accordingly.

### Examples

The following code sets the field `secret_backend_command` in the configuration file `datadog.yaml`:

```ruby
 default_attributes(
   'datadog' => {
     'extra_config' => {
       'secret_backend_command' => '/sbin/local-secrets'
     }
   }
 )
````

The `secret_backend_command` can also be set using:

```text
default['datadog']['extra_config']['secret_backend_command'] = '/sbin/local-secrets'
```

For nested attributes, use object syntax. The following code sets the field `logs_config` in the configuration file `datadog.yaml`:

```ruby
default['datadog']['extra_config']['logs_config'] = { 'use_port_443' => true }
```

### AWS OpsWorks Chef deployment{% #aws-opsworks-chef-deployment %}

Follow the steps below to deploy the Datadog Agent with Chef on AWS OpsWorks:

1. Add Chef custom JSON:

```json
{"datadog":{"agent_major_version": 7, "api_key": "<API_KEY>", "application_key": "<APP_KEY>"}}
```
Include the recipe in the `install-lifecycle` recipe:
```ruby
include_recipe '::dd-agent'
```

### Integrations{% #integrations %}

Enable Agent integrations by including the recipe and configuration details in your role's run-list and attributes. **Note**: You can use the `datadog_monitor` resource for enabling Agent integrations without a recipe.

Associate your recipes with the desired `roles`, for example `role:chef-client` should contain `datadog::dd-handler` and `role:base` should start the Agent with `datadog::dd-agent`. Below is an example role with the `dd-handler`, `dd-agent`, and `mongo` recipes:

```ruby
name 'example'
description 'Example role using DataDog'

default_attributes(
  'datadog' => {
    'agent_major_version' => 7,
    'api_key' => '<YOUR_DD_API_KEY>',
    'application_key' => '<YOUR_DD_APP_KEY>',
    'mongo' => {
      'instances' => [
        {'host' => 'localhost', 'port' => '27017'}
      ]
    }
  }
)

run_list %w(
  recipe[datadog::dd-agent]
  recipe[datadog::dd-handler]
  recipe[datadog::mongo]
)
```

**Note**: `data_bags` are not used in this recipe because it is unlikely to have multiple API keys with only one application key.

### Versions{% #versions %}

By default, the current major version of this cookbook installs Agent v7. The following attributes are available to control the Agent version installed:

| Parameter              | Description                                                                                                                                                                         |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `agent_major_version`  | Pin the major version of the Agent to 5, 6, or 7 (default).                                                                                                                         |
| `agent_version`        | Pin a specific Agent version (recommended).                                                                                                                                         |
| `agent_package_action` | (Linux only) Defaults to `'install'` (recommended), `'upgrade'` to get automatic Agent updates (not recommended, use the default and change the pinned `agent_version` to upgrade). |
| `agent_flavor`         | (Linux only) Defaults to `'datadog-agent'` to install the datadog-agent, can be set to `'datadog-iot-agent'` to install the IOT agent.                                              |

See the sample [attributes/default.rb](https://github.com/DataDog/chef-datadog/blob/master/attributes/default.rb) for your cookbook version for all available attributes.

#### Upgrade{% #upgrade %}

Some attribute names have changed from version 3.x to 4.x of the cookbook. Use this reference table to update your configuration:

| Action                       | Cookbook 3.x                                          | Cookbook 4.x                              |
| ---------------------------- | ----------------------------------------------------- | ----------------------------------------- |
| Install Agent 7.x            | Not supported                                         | `'agent_major_version' => 7`              |
| Install Agent 6.x            | `'agent6' => true`                                    | `'agent_major_version' => 6`              |
| Install Agent 5.x            | `'agent6' => false`                                   | `'agent_major_version' => 5`              |
| Pin agent version            | `'agent_version'` or `'agent6_version'`               | `'agent_version'` for all versions        |
| Change package_action        | `'agent_package_action'` or `'agent6_package_action'` | `'agent_package_action'` for all versions |
| Change APT repo URL          | `'aptrepo'` or `'agent6_aptrepo'`                     | `'aptrepo'` for all versions              |
| Change APT repo distribution | `'aptrepo_dist'` or `'agent6_aptrepo_dist'`           | `'aptrepo_dist'` for all versions         |
| Change YUM repo              | `'yumrepo'` or `'agent6_yumrepo'`                     | `'yumrepo'` for all versions              |
| Change SUSE repo             | `'yumrepo_suse'` or `'agent6_yumrepo_suse'`           | `'yumrepo_suse'` for all versions         |

Use one of the following methods to upgrade from Agent v6 to v7:

- Set `agent_major_version` to `7`, `agent_package_action` to `install`, and pin a specific v7 version as `agent_version` (recommended).
- Set `agent_major_version` to `7` and `agent_package_action` to `upgrade`.

The following example upgrades from Agent v6 to v7. The same applies if you are upgrading from Agent v5 to v6.

```ruby
default_attributes(
  'datadog' => {
    'agent_major_version' => 7,
    'agent_version' => '7.25.1',
    'agent_package_action' => 'install',
  }
)
```

#### Downgrade{% #downgrade %}

To downgrade the Agent version, set the `'agent_major_version'`, `'agent_version'`, and `'agent_allow_downgrade'`.

The following example downgrades to Agent v6. The same applies if you are downgrading to Agent v5.

```ruby
  default_attributes(
    'datadog' => {
      'agent_major_version' => 6,
      'agent_version' => '6.10.0',
      'agent_allow_downgrade' => true
    }
  )
```

#### Uninstall{% #uninstall %}

To uninstall the Agent, remove the `dd-agent` recipe and add the `remove-dd-agent` recipe with no attributes.

#### Custom Agent repository{% #custom-agent-repository %}

To use an Agent from a custom repository, you can set the `aptrepo` option.

By default, this option is equal to `[signed-by=/usr/share/keyrings/datadog-archive-keyring.gpg] apt.datadoghq.com`. If a custom value is set, another `signed-by` keyring can also be set `[signed-by=custom-repo-keyring-path] custom-repo`.

The example below uses the staging repository:

```ruby
  default_attributes(
    'datadog' => {
      'aptrepo' => '[signed-by=/usr/share/keyrings/datadog-archive-keyring.gpg] apt.datad0g.com',
    }
  }
```

### Recipes{% #recipes %}

Access the [Datadog Chef recipes on GitHub](https://github.com/DataDog/chef-datadog/tree/master/recipes).

#### Default{% #default %}

The [default recipe](https://github.com/DataDog/chef-datadog/blob/master/recipes/default.rb) is a placeholder.

#### Agent{% #agent %}

The [dd-agent recipe](https://github.com/DataDog/chef-datadog/blob/master/recipes/dd-agent.rb) installs the Datadog Agent on the target system, sets your [Datadog API key](https://app.datadoghq.com/organization-settings/api-keys), and starts the service to report on local system metrics.

**Note**: Windows users upgrading the Agent from versions <= 5.10.1 to >= 5.12.0, set the `windows_agent_use_exe` attribute to `true`. For more details, see the [dd-agent wiki](https://github.com/DataDog/dd-agent/wiki/Windows-Agent-Installation).

#### Handler{% #handler %}

The [dd-handler recipe](https://github.com/DataDog/chef-datadog/blob/master/recipes/dd-handler.rb) installs the [chef-handler-datadog](https://rubygems.org/gems/chef-handler-datadog) gem and invokes the handler at the end of a Chef run to report the details to the news feed.

#### DogStatsD{% #dogstatsd %}

To install a language-specific library that interacts with DogStatsD:

- Ruby: [dogstatsd-ruby recipe](https://github.com/DataDog/chef-datadog/blob/master/recipes/dogstatsd-ruby.rb)
- Python: Add a dependency on the `poise-python` cookbook to your custom/wrapper cookbook, and use the resource below. For more details, see the [poise-python repository](https://github.com/poise/poise-python).
  ```ruby
  python_package 'dogstatsd-python' # assumes python and pip are installed
  ```

#### Tracing{% #tracing %}

To install a language-specific library for application tracing (APM):

- Ruby: [ddtrace-ruby recipe](https://github.com/DataDog/chef-datadog/blob/master/recipes/ddtrace-ruby.rb)
- Python: Add a dependency on the `poise-python` cookbook to your custom/wrapper cookbook, and use the resource below. For more details, see the [poise-python repository](https://github.com/poise/poise-python).
  ```ruby
  python_package 'ddtrace' # assumes python and pip are installed
  ```

#### Integrations{% #integrations-1 %}

There are many [recipes](https://github.com/DataDog/chef-datadog/tree/master/recipes) to assist you with deploying Agent integration configuration files and dependencies.

#### System-probe{% #system-probe %}

The [system-probe recipe](https://github.com/DataDog/chef-datadog/blob/master/recipes/system-probe.rb) is automatically included by default. It writes the `system-probe.yaml` file. This behavior can be disabled by setting `node['datadog']['system_probe']['manage_config']` to false.

To enable [Network Performance Monitoring](https://github.com/DataDog/chef-datadog/tree/master/recipes) (NPM) in `system-probe.yaml`, set `node['datadog']['system_probe']['network_enabled']` to true.

To enable [Universal Service Monitoring](https://github.com/DataDog/chef-datadog/tree/master/recipes) (USM) in `system-probe.yaml`, set `node['datadog']['system_probe']['service_monitoring_enabled']` to true.

**Note for Windows users**: NPM is supported on Windows with Agent v6.27+ and v7.27+. It ships as an optional component that is only installed if `node['datadog']['system_probe']['network_enabled']` is set to true when the Agent is installed or upgraded. Because of this, existing installations might need to do an uninstall and reinstall of the Agent once to install the NPM component, unless the Agent is upgraded at the same time.

### Resources{% #resources %}

#### Integrations without recipes{% #integrations-without-recipes %}

Use the `datadog_monitor` resource for enabling Agent integrations without a recipe.

##### Actions{% #actions %}

- `:add`: (default) Enables the integration by setting up the configuration file, adding the correct permissions to the file, and restarting the Agent.
- `:remove`: Disables an integration.

##### Syntax{% #syntax %}

```ruby
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
  config_name                       String # default value: 'conf'
  action                            Symbol # defaults to :add
end
```

##### Properties{% #properties %}

| Property                   | Description                                                                                                                                                                                                                                                                                   |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `'name'`                   | The name of the Agent integration to configure and enable.                                                                                                                                                                                                                                    |
| `instances`                | The fields used to fill values under the `instances` section in the integration configuration file.                                                                                                                                                                                           |
| `init_config`              | The fields used to fill values under the the `init_config` section in the integration configuration file.                                                                                                                                                                                     |
| `logs`                     | The fields used to fill values under the the `logs` section in the integration configuration file.                                                                                                                                                                                            |
| `use_integration_template` | Set to `true` (recommended) to use the default template, which writes the values of `instances`, `init_config`, and `logs` in the YAML under their respective keys. This defaults to `false` for backward compatibility, but may default to `true` in a future major version of the cookbook. |
| `config_name`              | The filename used when creating an integrations configuration file. Overriding this property allows the creation of multiple configuration files for a single integration. This defaults to `conf`, which creates a configuration file named `conf.yaml`.                                     |

##### Example{% #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 to restart the Agent.

**Note**: The Agent installation must be above this recipe in the run list.

```ruby
include_recipe '::dd-agent'

datadog_monitor 'elastic' do
  instances  [{'url' => 'http://localhost:9200'}]
  use_integration_template true
  notifies :restart, 'service[datadog-agent]' if node['datadog']['agent_start']
end
```

See the [Datadog integration Chef recipes](https://github.com/DataDog/chef-datadog/tree/master/recipes) for additional examples.

#### Integration versions{% #integration-versions %}

To install a specific version of a Datadog integration, use the `datadog_integration` resource.

##### Actions{% #actions-1 %}

- `:install`: (default) Installs an integration with the specified version.
- `:remove`: Removes an integration.

##### Syntax{% #syntax-1 %}

```ruby
datadog_integration 'name' do
  version                      String         # version to install for :install action
  action                       Symbol         # defaults to :install
  third_party                  [true, false]  # defaults to :false
end
```

##### Properties{% #properties-1 %}

- `'name'`: The name of the Agent integration to install, for example: `datadog-apache`.
- `version`: The version of the integration to install (only required with the `:install` action).
- `third_party`: Set to false if installing a Datadog integration, true otherwise. Available for Datadog Agents version 6.21/7.21 and higher only.

##### Example{% #example-1 %}

This example installs version `1.11.0` of the ElasticSearch integration by using the `datadog_integration` resource.

**Note**: The Agent installation must be above this recipe in the run list.

```ruby
include_recipe '::dd-agent'

datadog_integration 'datadog-elastic' do
  version '1.11.0'
end
```

To get the available versions of the integrations, see the integration-specific `CHANGELOG.md` in the [integrations-core repository](https://github.com/DataDog/integrations-core).

**Note**: For Chef Windows users, the `chef-client` must have read access to the `datadog.yaml` file when the `datadog-agent` binary available on the node is used by this resource.

### Development{% #development %}

#### Dockerized environment{% #dockerized-environment %}

To build a Docker environment with which to run kitchen tests, use the files under `docker_test_env`:

```
cd docker_test_env
docker build -t chef-datadog-test-env .
```

To run the container use:

```gdscript3
docker run -d -v /var/run/docker.sock:/var/run/docker.sock chef-datadog-test-env
```

Then attach a console to the container or use the VS Code remote-container feature to develop inside the container.

To run kitchen-docker tests from within the container:

```mysql
# Note: Also set KITCHEN_DOCKER_HOSTNAME=host.docker.internal if on MacOS or Windows
# Run this under a login shell (otherwise `bundle` won't be found)
KITCHEN_LOCAL_YAML=kitchen.docker.yml bundle exec rake circle
```