You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+56-4Lines changed: 56 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,10 @@ Datadog Cookbook
16
16
17
17
Chef recipes to deploy Datadog's components and configuration automatically.
18
18
19
-
This cookbook includes experimental support of the beta version of the Datadog Agent 6.0, please refer to
20
-
the [inline docs](https://github.com/DataDog/chef-datadog/blob/v2.13.0/attributes/default.rb#L31-L68)
19
+
This cookbook includes new support for Datadog Agent version 6.0, please refer to
20
+
the [inline docs](https://github.com/DataDog/chef-datadog/blob/v2.14.0/attributes/default.rb#L31-L68)
21
21
for more details on the supported platforms and how to use it.
22
-
Log collection is now available with agent 6.0, please refer to the [inline docs](https://github.com/DataDog/chef-datadog/blob/v2.13.0/attributes/default.rb#L371-L376) to enable it.
22
+
Log collection is now available with agent 6.0, please refer to the [inline docs](https://github.com/DataDog/chef-datadog/blob/v2.14.0/attributes/default.rb#L371-L376) to enable it.
23
23
24
24
For general information on the Datadog Agent 6, please refer to the [datadog-agent](https://github.com/DataDog/datadog-agent/) repo.
25
25
@@ -108,9 +108,59 @@ There are many other integration-specific recipes, that are meant to assist in d
108
108
Usage
109
109
=====
110
110
111
+
### Agent6 Note
112
+
Please note the cookbook now supports installing both Agent5 and Agent6 of the datadog agent on debian and RHEL based linux distributions (not yet supported on windows). By default versions `<=1.x` of the cookbook will default to install Agent5, you may however override this behavior with the `node['datadog']['agent6']` attribute.
113
+
```
114
+
default_attributes(
115
+
'datadog' => {
116
+
'agent6' => true
117
+
}
118
+
)
119
+
```
120
+
121
+
Additional attributes are available to have finer control over how you install agent6. These are agent6 counterparts to several well known agent5 attributes (code [here](https://github.com/DataDog/chef-datadog/blob/master/attributes/default.rb#L31-L69)):
122
+
*`agent6_version`: should allow you to pin the agent version.
123
+
*`agent6_package_action`: defaults to `'install'`, may be set to `'upgrade'` to always upgrade to latest.
124
+
*`agent6_aptrepo`: desired APT repo for the agent. Defaults to `http://apt.datadoghq.com`
125
+
*`agent6_aptrepo_dist`: desired distribution for the APT repo. Defaults to `stable`
126
+
*`agent6_yumrepo`: desired YUM repo for the agent. Defaults to `https://yum.datadoghq.com/stable/6/x86_64/`
127
+
128
+
Should wish to add additional elements to the agent6 configuration file, typically `/etc/datadog/datadog.yaml` you may use the `node['datadog']['extra_config']` attribute. This attribute is a hash and will be marshaled into the configuration file accordingly. For instance, to enable the `apm` tracing agent bundled with agent6:
129
+
```
130
+
default_attributes(
131
+
'datadog' => {
132
+
'extra_config' => {
133
+
'apm_config' => {
134
+
'enabled' => true
135
+
}
136
+
}
137
+
}
138
+
)
139
+
```
140
+
141
+
or to enable both process agent and apm:
142
+
```
143
+
default_attributes(
144
+
'datadog' => {
145
+
'extra_config' => {
146
+
'apm_config' => {
147
+
'enabled' => true
148
+
},
149
+
'process_config' => {
150
+
'enabled' => 'disabled'
151
+
}
152
+
}
153
+
}
154
+
)
155
+
```
156
+
NB: please take a look at the process and apm agents for more details regarding configuration options. [APM Trace Agent](https://github.com/DataDog/datadog-trace-agent) and [Process Agent](https://github.com/DataDog/datadog-process-agent)
157
+
158
+
159
+
### Instructions
160
+
111
161
1. Add this cookbook to your Chef Server, either by installing with knife or by adding it to your Berksfile:
112
162
```
113
-
cookbook 'datadog', '~> 2.7.0'
163
+
cookbook 'datadog', '~> 2.14.0'
114
164
```
115
165
2. Add your API Key either:
116
166
* as a node attribute via an `environment` or `role`, or
@@ -137,6 +187,8 @@ Usage
137
187
recipe[datadog::dd-handler]
138
188
)
139
189
```
190
+
NB: remember to set `agent6` attribute in the `datadog` hash if you'd like to install agent6.
191
+
140
192
5. Wait until `chef-client` runs on the target node (or trigger chef-client manually if you're impatient)
141
193
142
194
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.
0 commit comments