To reuse the configuration of an existing Agent:
@@ -173,6 +173,7 @@ Set-AzVMExtension -Name "DatadogAgent" -Publisher "Datadog.Agent" -Type "Datadog
{{< /code-block >}}
[100]: https://learn.microsoft.com/powershell/module/az.compute/set-azvmextension
+[101]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_windows.yaml.example
{{% /tab %}}
{{% tab "Linux" %}}
@@ -206,7 +207,7 @@ The protected settings include:
This example shows how to specify a configuration for the Datadog Agent to use.
- The Datadog Agent configuration URI must be an Azure blob storage URI.
- The Datadog Linux Agent Azure Extension checks that the `agentConfiguration` URI comes from the `.blob.core.windows.net` domain.
-- The Datataog Agent configuration should be created from the `/etc/datadog-agent/` folder.
+- The Datataog Agent configuration should be created from the `/etc/datadog-agent/` folder (see the [example Agent configuration file for Linux][201] for all available configuration options).
To reuse the configuration of an existing Agent by saving its
/etc/datadog-agent folder as a ZIP file:
@@ -230,6 +231,7 @@ az vm extension set --publisher "Datadog.Agent" --name "DatadogLinuxAgent" --ver
[200]: https://learn.microsoft.com/cli/azure/vm/extension
+[201]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
{{% /tab %}}
{{< /tabs >}}
diff --git a/hugo/content/en/logs/guide/increase-number-of-log-files-tailed.md b/hugo/content/en/logs/guide/increase-number-of-log-files-tailed.md
index 30b895bc7a1..17d367df82a 100644
--- a/hugo/content/en/logs/guide/increase-number-of-log-files-tailed.md
+++ b/hugo/content/en/logs/guide/increase-number-of-log-files-tailed.md
@@ -24,9 +24,9 @@ logs_config:
For containerized environments you can set the `DD_LOGS_CONFIG_OPEN_FILES_LIMIT` environment variable.
-The default value varies depending on the Agent version and operating system. To check the default value for your Agent version, see the [config_template.yaml file][1] in the Datadog Agent repository. Be sure to select the tag corresponding to your Agent version to see the correct defaults.
+The default value varies depending on the Agent version and operating system. To check the default value for your Agent version, see the [example Agent configuration files][1] in the Datadog Agent repository. Open the file for your operating system. Be sure to select the tag corresponding to your Agent version to see the correct defaults.
**Note**: Increasing the tailed logs files limit might increase the resource consumption of the Agent.
-[1]: https://github.com/DataDog/datadog-agent/blob/369a8dbb39dc6e8601d82c8f43caaaf88d6a0a55/pkg/config/config_template.yaml#L987-L993
+[1]: https://github.com/DataDog/datadog-agent/tree/main/pkg/config/example
diff --git a/hugo/content/en/metrics/types.md b/hugo/content/en/metrics/types.md
index eec9400b6a1..f6383c5ba6a 100644
--- a/hugo/content/en/metrics/types.md
+++ b/hugo/content/en/metrics/types.md
@@ -118,11 +118,10 @@ If you send `X` values for a HISTOGRAM metric `
` in a given time in
**Notes**:
- Configure which aggregations you want to send to Datadog with the `histogram_aggregates` parameter in your [`datadog.yaml` configuration file][1]. By default, only `max`, `median`, `avg`, and `count` aggregations are sent to Datadog. `sum` and `min` are also available.
-- Configure which percentile aggregation you want to send to Datadog with the `histogram_percentiles` parameter in your [`datadog.yaml` configuration file][2]. By default, only the `95percentile` is sent to Datadog.
+- Configure which percentile aggregation you want to send to Datadog with the `histogram_percentiles` parameter in your [`datadog.yaml` configuration file][1]. By default, only the `95percentile` is sent to Datadog.
-[1]: https://github.com/DataDog/datadog-agent/blob/04d8ae9dd4bc6c7a64a8777e8a38127455ae3886/pkg/config/config_template.yaml#L106-L114
-[2]: https://github.com/DataDog/datadog-agent/blob/04d8ae9dd4bc6c7a64a8777e8a38127455ae3886/pkg/config/config_template.yaml#L116-L121
+[1]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
{{% /tab %}}
{{% tab "DISTRIBUTION" %}}
diff --git a/hugo/content/en/network_monitoring/devices/guide/cluster-agent.md b/hugo/content/en/network_monitoring/devices/guide/cluster-agent.md
index 56bdba6baba..9e6b1de0e9f 100644
--- a/hugo/content/en/network_monitoring/devices/guide/cluster-agent.md
+++ b/hugo/content/en/network_monitoring/devices/guide/cluster-agent.md
@@ -209,6 +209,7 @@ clusterAgent:
#
datadog_cluster_yaml:
+ # See here for all `network_devices.autodiscovery` configs: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
autodiscovery:
workers: 2
discovery_interval: 10
diff --git a/hugo/content/en/network_monitoring/devices/snmp_metrics.md b/hugo/content/en/network_monitoring/devices/snmp_metrics.md
index 44930b683c4..fe8e97b7851 100644
--- a/hugo/content/en/network_monitoring/devices/snmp_metrics.md
+++ b/hugo/content/en/network_monitoring/devices/snmp_metrics.md
@@ -113,7 +113,7 @@ To use Autodiscovery with Network Device Monitoring:
2. Edit the [`datadog.yaml`][8] Agent configuration file to include all the subnets for Datadog to scan. The following sample config provides required parameters, default values, and examples for Autodiscovery.
-3. Optionally, enable de-duplication of devices during Autodiscovery of the Agent. This feature is disabled by default and requires Agent version `7.67+`.
+3. Optionally, enable de-duplication of devices during Autodiscovery of the Agent. This feature is disabled by default and requires Agent version 7.67+. For details, see the `use_deduplication` parameter in the [example Agent configuration file][11].
```yaml
network_devices:
@@ -231,3 +231,4 @@ For all available `interface_configs` options, see the [sample snmp.d/conf.yaml]
[8]: /agent/configuration/agent-configuration-files/?tab=agentv6v7#agent-main-configuration-file
[9]: https://github.com/DataDog/datadog-agent/blob/51dd4482466cc052d301666628b7c8f97a07662b/pkg/config/config_template.yaml#L855
[10]: /agent/configuration/agent-commands/#agent-status-and-information
+[11]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
diff --git a/hugo/content/en/network_monitoring/netflow/_index.md b/hugo/content/en/network_monitoring/netflow/_index.md
index 1b7fcf57859..01dc9104aa5 100644
--- a/hugo/content/en/network_monitoring/netflow/_index.md
+++ b/hugo/content/en/network_monitoring/netflow/_index.md
@@ -108,13 +108,13 @@ From the [{{< ui >}}Enrichment{{< /ui >}} settings page][10], click {{< ui >}}+
Enable Reverse DNS private IP enrichment to perform DNS lookups for hostnames associated with source or destination IP addresses. When enabled, the Agent conducts reverse DNS lookups on source and destination IPs within private address ranges, enriching NetFlow records with the corresponding hostnames.
-By [default][7], the Reverse DNS IP enrichment in your `datadog.yaml` file is disabled. To enable, see the [Configuration](#configuration) section of this page.
+By default, the Reverse DNS IP enrichment in your [`datadog.yaml` file][7] is disabled. To enable, see the [Configuration](#configuration) section of this page.
Search for DNS in the {{< ui >}}+ Filter{{< /ui >}} menu to locate flows associated with Reverse DNS IP enrichment:
{{< img src="network_device_monitoring/netflow/dns_ip_enrichmen_2.png" alt="Filter menu enhanced to show the reverse DNS destination and source facets" width="100%" >}}
-**Note**: Reverse DNS entries are cached and subject to rate limiting to minimize DNS queries and reduce the load on DNS servers. For more configuration options, including modifying default caching and rate limiting, see the [full configuration file][8].
+**Note**: Reverse DNS entries are cached and subject to rate limiting to minimize DNS queries and reduce the load on DNS servers. For more configuration options, including modifying default caching and rate limiting, see the `reverse_dns_enrichment` section of the [example Agent configuration file][7].
## IP details
@@ -376,8 +376,7 @@ Use the `netstat -s` command to see if there are any dropped UDP packets:
[4]: /agent/configuration/agent-commands/?tab=agentv6v7#start-stop-and-restart-the-agent
[5]: https://app.datadoghq.com/devices/netflow
[6]: /monitors/types/netflow/
-[7]: https://github.com/DataDog/datadog-agent/blob/f6ae461a7d22aaf398de5a94d9330694d69560d6/pkg/config/config_template.yaml#L4201
-[8]: https://github.com/DataDog/datadog-agent/blob/f6ae461a7d22aaf398de5a94d9330694d69560d6/pkg/config/config_template.yaml#L4203-L4275
+[7]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
[9]: /network_monitoring/devices/troubleshooting#traps-or-flows-not-being-received-at-all
[10]: https://app.datadoghq.com/devices/settings/enrichment/ip
[11]: /network_monitoring/network_path/setup/#dynamic-tests-for-netflow-experimental
diff --git a/hugo/content/en/network_monitoring/network_path/setup.md b/hugo/content/en/network_monitoring/network_path/setup.md
index 59366a1cd99..eed4c04c8e1 100644
--- a/hugo/content/en/network_monitoring/network_path/setup.md
+++ b/hugo/content/en/network_monitoring/network_path/setup.md
@@ -374,7 +374,7 @@ Agent `v7.73+` is required.
3. Restart the Agent after making these configuration changes to start seeing network paths.
-[3]: https://github.com/DataDog/datadog-agent/blob/2c8d60b901f81768f44a798444af43ae8d338843/pkg/config/config_template.yaml#L1731
+[3]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
{{% /tab %}}
{{% tab "Windows" %}}
@@ -442,7 +442,7 @@ Agent `v7.73+` is required.
3. Restart the Agent after making these configuration changes to start seeing network paths.
-[3]: https://github.com/DataDog/datadog-agent/blob/2c8d60b901f81768f44a798444af43ae8d338843/pkg/config/config_template.yaml#L1731
+[3]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_windows.yaml.example
{{% /tab %}}
{{% tab "Helm" %}}
diff --git a/hugo/content/en/opentelemetry/mapping/service_entry_spans.md b/hugo/content/en/opentelemetry/mapping/service_entry_spans.md
index 64937032c45..055891fe5c7 100644
--- a/hugo/content/en/opentelemetry/mapping/service_entry_spans.md
+++ b/hugo/content/en/opentelemetry/mapping/service_entry_spans.md
@@ -33,7 +33,7 @@ The new service-entry span identification logic can be enabled by setting the `t
The new service-entry span identification logic can be enabled by adding `"enable_otlp_compute_top_level_by_span_kind"` to [apm_config.features][1] in the Datadog Agent config.
-[1]: https://github.com/DataDog/datadog-agent/blob/7.53.0/pkg/config/config_template.yaml#L1585-L1591
+[1]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/example/datadog-agent_linux.yaml.example
{{% /tab %}}
{{< /tabs >}}
diff --git a/hugo/content/en/opentelemetry/setup/ddot_collector/install/linux.md b/hugo/content/en/opentelemetry/setup/ddot_collector/install/linux.md
index a069450fb91..9d13bfe3e5a 100644
--- a/hugo/content/en/opentelemetry/setup/ddot_collector/install/linux.md
+++ b/hugo/content/en/opentelemetry/setup/ddot_collector/install/linux.md
@@ -116,7 +116,7 @@ DDOT automatically binds the OpenTelemetry Collector to ports 4317 (grpc) and 43
Enabling these features may incur additional charges. Review the
pricing page and talk to your Customer Success Manager before proceeding.
Enabling these features may incur additional charges. Review the
pricing page and talk to your Customer Success Manager before proceeding.