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: content/en/agent/configuration/agent-configuration-files.md
+8-49Lines changed: 8 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,9 @@ algolia:
11
11
12
12
---
13
13
14
-
## Agent main configuration file
14
+
## Main configuration file
15
15
16
-
The Agent v6 configuration file uses **YAML** to better support complex configurations, and to provide a consistent configuration experience, as Checks also use YAML configuration files. Therefore, `datadog.conf` (v5) is retired in favor of `datadog.yaml` (v6).
17
-
18
-
{{< tabs >}}
19
-
{{% tab "Agent v6 & v7" %}}
16
+
The location of the Agent configuration file differs depending on the operating system.
| Windows Server 2008, Vista and newer |`%ProgramData%\Datadog\datadog.conf`|
36
-
| Windows Server 2003, XP or older |`\\Documents and Settings\All Users\Application Data\Datadog\datadog.conf`|
37
-
38
-
{{% /tab %}}
39
-
{{< /tabs >}}
40
-
41
-
See the [sample `config_template.yaml` file][2] for all available configuration options.
25
+
See the [sample `config_template.yaml` file][1] for all available configuration options.
42
26
43
27
## Agent configuration directory
44
28
45
-
Prior releases of Datadog Agent stored configuration files in `/dd-agent/conf.d/`. Starting with the 6.0 release, configuration files are stored in `/etc/datadog-agent/conf.d/<CHECK_NAME>.d/`.
46
-
47
-
{{< tabs >}}
48
-
{{% tab "Agent v6 & v7" %}}
29
+
Configuration files for Agent checks and integrations are stored in the `conf.d` directory. The location of the directory differs depending on the operating system.
@@ -61,7 +42,7 @@ Prior releases of Datadog Agent stored configuration files in `/dd-agent/conf.d/
61
42
| Ubuntu |`/etc/datadog-agent/conf.d/`|
62
43
| Windows |`%ProgramData%\Datadog\conf.d`|
63
44
64
-
### Checks configuration files for Agent 6
45
+
### Check configuration files
65
46
66
47
An example for each Agent check configuration file is found in the `conf.yaml.example` file in the corresponding `<CHECK_NAME>.d/` folder. Rename this file to `conf.yaml` to enable the associated check. **Note**: The Agent loads valid YAML files contained in the folder: `/etc/datadog-agent/conf.d/<CHECK_NAME>.d/`. This allows complex configurations to be broken down into multiple files. For example, a configuration for the `http_check` might look like this:
67
48
@@ -83,31 +64,9 @@ Autodiscovery template files are stored in the configuration folder with the `au
83
64
84
65
For log collection, the Agent does not accept multiple YAML files that point to the same log source to prevent duplicate logs from being sent to Datadog. In the case where there is more than one YAML file that points to the same log source, the Agent considers the files in alphabetical order and uses the first file.
85
66
86
-
To preserve backwards compatibility, the Agent still picks up configuration files in the form `/etc/dd-agent/conf.d/<CHECK_NAME>.yaml`, but migrating to the new layout is strongly recommended.
| Windows Server 2008, Vista and newer |`%ProgramData%\Datadog\conf.d`|
103
-
| Windows Server 2003, XP or older |`\\Documents and Settings\All Users\Application Data\Datadog\conf.d`|
104
-
105
-
{{% /tab %}}
106
-
{{< /tabs >}}
107
-
108
67
## JMX configuration file
109
68
110
-
JMX Agent checks have an additional `metrics.yaml` file in their configuration folder. It is a list of all the beans that the Datadog Agent collects by default. This way, you do not need to list all of the beans manually when you configure a check through [Docker labels or k8s annotations][1].
69
+
JMX Agent checks have an additional `metrics.yaml` file in their configuration folder. It is a list of all the beans that the Datadog Agent collects by default. This way, you do not need to list all of the beans manually when you configure a check through [Docker labels or k8s annotations][2].
0 commit comments