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
[DOCS-15417] Point to new example Agent config files (DataDog#39331)
* [DOCS-15417] Add back removed references, and update per-OS config references
* Replace pinned-version and -line-number links to old config-template file
* A few more from DataDog#39062
| Windows |`%ProgramData%\Datadog\datadog.yaml`|[`datadog-agent_windows.yaml.example`][6]|
25
25
26
26
## Agent configuration directory
27
27
@@ -69,4 +69,8 @@ For log collection, the Agent does not accept multiple YAML files that point to
69
69
70
70
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].
Copy file name to clipboardExpand all lines: hugo/content/en/agent/guide/datadog-agent-manager-windows.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,6 +115,8 @@ The log page displays the Agent logs being output to `agent.log`. Logs can be so
115
115
116
116
The settings page displays the contents of the Agent's main configuration file `datadog.yaml`. You can edit this file directly from the Datadog Agent Manager. After making a change, click {{< ui >}}Save{{< /ui >}} in the upper right then [restart the Agent](#restart-agent).
117
117
118
+
For a full list of available options, see the [example `datadog.yaml` file for Windows][6].
119
+
118
120
### Checks
119
121
120
122
#### Manage checks
@@ -143,3 +145,4 @@ Clicking {{< ui >}}Restart Agent{{< /ui >}} from the left navigation bar restart
Copy file name to clipboardExpand all lines: hugo/content/en/agent/logs/_index.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,8 @@ logs_config:
39
39
force_use_http: true
40
40
{{< /code-block >}}
41
41
42
+
For all available configuration options, see the [example Agent configuration files][6] for your operating system.
43
+
42
44
<divclass="alert alert-info">Starting with Agent v6.19+/v7.19+, HTTPS transport is the default transport used. For more details, see <ahref="/agent/logs/log_transport/">Agent transport</a>.</div>
43
45
44
46
To send logs with **environment variables**, configure the following:
@@ -255,6 +257,7 @@ For both file and journald tailer types, if an `end` or `beginning` position is
Copy file name to clipboardExpand all lines: hugo/content/en/agent/supported_platforms/linux.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The Datadog Agent configuration file is located in `/etc/datadog-agent/datadog.y
58
58
-`proxy`: HTTP/HTTPS proxy endpoints for outbound traffic (see [Datadog Agent Proxy Configuration][8])
59
59
- Default tags, log level, and Datadog configurations
60
60
61
-
A fully commented reference file, located in `/etc/datadog-agent/datadog.yaml.example`, lists every available option for comparison or to copy and paste.
61
+
A fully commented reference file, located in `/etc/datadog-agent/datadog.yaml.example`, lists every available option for comparison or to copy and paste. Alternatively, see the [example Agent configuration file for Linux][11] on GitHub.
62
62
63
63
### Integration files
64
64
Configuration files for integrations live in `/etc/datadog-agent/conf.d/`. Each integration has its own sub-directory, `<INTEGRATION>.d/`, that contains:
@@ -158,3 +158,4 @@ See the instructions on how to [add packages to the embedded Agent][3] for more
Copy file name to clipboardExpand all lines: hugo/content/en/agent/supported_platforms/osx.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ The [Datadog Agent configuration file][7] is located in `/opt/datadog-agent`. Th
65
65
-`proxy`: HTTP/HTTPS proxy endpoints for outbound traffic (see [Datadog Agent Proxy Configuration][9])
66
66
- Default tags, log levels, and Datadog configurations.
67
67
68
-
A fully commented reference file, located in `/opt/datadog-agent/etc/datadog.yaml.example`, lists every available option for comparison or copy-paste.
68
+
A fully commented reference file, located in `/opt/datadog-agent/etc/datadog.yaml.example`, lists every available option for comparison or copy-paste. Alternatively, see the [example Agent configuration file for macOS][10] on GitHub.
69
69
70
70
### Integration files
71
71
Configuration files for integrations are found in `/opt/datadog-agent/etc/conf.d/`. Each integration has its own sub-directory, `<INTEGRATION>.d/`, which contains:
@@ -105,4 +105,5 @@ See the instructions on how to [add packages to the embedded Agent][3] for more
Copy file name to clipboardExpand all lines: hugo/content/en/agent/supported_platforms/sccm.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Microsoft SCCM (Systems Center Configuration Manager) is a configuration managem
61
61
62
62
SCCM packages allow you to deploy configuration files to your Datadog Agents, overwriting their default settings. An Agent configuration consists of a `datadog.yaml` configuration file and optional `conf.yaml` files for each integration. You must create a package for each configuration file you want to deploy.
63
63
64
-
1. Collect your `datadog.yaml` and `conf.yaml` files in a local SCCM machine folder.
64
+
1. Collect your `datadog.yaml` and `conf.yaml` files in a local SCCM machine folder. See the [example Agent configuration file for Windows][4] for all available configuration options.
65
65
1. Create an SCCM Package and select {{< ui >}}Standard program{{< /ui >}}.
66
66
1. Select the location that contains the configuration file that you want to deploy to your Agents.
67
67
1. Select a [Device collection][5] to deploy the changes to.
@@ -83,5 +83,6 @@ Restart the Agent service to observe your configuration changes:
Copy file name to clipboardExpand all lines: hugo/content/en/agent/supported_platforms/windows.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ Set the `/log <FILENAME>` msiexec option to configure an installation log file.
108
108
The main Agent configuration file is located at
109
109
`C:\ProgramData\Datadog\datadog.yaml`. This file is used for host-wide settings such as the API key, selected Datadog site, proxy parameters, host tags, and log level.
110
110
111
-
There is also a `datadog.yaml.example` file in the same directory, which is a fully commented reference with all available configuration options, useful for reference and copying specific settings.
111
+
There is also a `datadog.yaml.example` file in the same directory, which is a fully commented reference with all available configuration options, useful for reference and copying specific settings. Alternatively, see the [example Agent configuration file for Windows][19] on GitHub.
112
112
113
113
114
114
Configuration files for integrations are in:
@@ -285,5 +285,6 @@ After configuration is complete, [restart the Agent][11].
0 commit comments