From dcd0e7f77f7b8d15839c2651752c10a0e6d96ee0 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 12:54:50 -0400 Subject: [PATCH 1/8] Add Squid proxy configuration for Datadog Agent Added configuration instructions for using Squid proxy with the Datadog Agent across different setups. --- content/en/agent/configuration/proxy_squid.md | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index a03e63fc81c..51e7275ba7c 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -72,6 +72,9 @@ net start squid ### Configure the Datadog Agent +{{< tabs >}} +{{% tab "Host" %}} + Modify the Agent's configuration file (`datadog.yaml`) to include the following: ```yaml @@ -82,6 +85,36 @@ proxy: After saving these changes, [restart the Agent][1]. +{{% /tab %}} +{{% tab "Operator" %}} + +Modify the DatadogAgent CR to include the following: + +```yaml +spec: + global: + proxy: + http: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 + https: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 +``` + +{{% /tab %}} +{{% tab "Helm" %}} + +Modify your `values.yaml` to include the following: + +```yaml +datadog: + env: + - name: DD_PROXY_HTTP + value: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 + - name: DD_PROXY_HTTPS + value: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 +``` + +{{% /tab %}} +{{< /tabs >}} + Verify that Datadog is able to receive the data from your Agent(s) by checking your [Infrastructure Overview][3]. ## Further Reading From ef9c8a203ab07f355a625a1e2d750f2dacc59a74 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 13:41:04 -0400 Subject: [PATCH 2/8] Apply suggestion from @github-actions[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- content/en/agent/configuration/proxy_squid.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index 51e7275ba7c..de533dac446 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -88,7 +88,7 @@ After saving these changes, [restart the Agent][1]. {{% /tab %}} {{% tab "Operator" %}} -Modify the DatadogAgent CR to include the following: +Modify the DatadogAgent custom resource to include the following: ```yaml spec: From 4becc7832a3b982433fb1dcf8f675f41d5689257 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 13:45:10 -0400 Subject: [PATCH 3/8] Update proxy configuration to include env section --- content/en/agent/configuration/proxy_squid.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index de533dac446..9898d336851 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -93,7 +93,7 @@ Modify the DatadogAgent custom resource to include the following: ```yaml spec: global: - proxy: + env: http: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 https: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 ``` From 7d2daa6944c6287b1ad0ec7babbb1aac955b44f1 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 14:40:19 -0400 Subject: [PATCH 4/8] Revise Squid proxy configuration instructions Updated instructions for configuring Squid proxy, including examples for wildcard and explicit domain access control. Clarified modification of the DatadogAgent custom resource. --- content/en/agent/configuration/proxy_squid.md | 25 ++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index 9898d336851..fc659e98092 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -21,7 +21,9 @@ Install Squid on a host that has connectivity to both your internal Agents and D To configure Squid, edit the configuration file. This file is usually located at `/etc/squid/squid.conf` on Linux or `C:\squid\etc\squid.conf` in Windows. For other operating systems, see [Agent configuration directory][6]. -Edit your `squid.conf` configuration file so that Squid is able to accept local traffic and forward it to the necessary Datadog intakes: +Edit your `squid.conf` configuration file so that Squid is able to accept local traffic and forward it to the necessary Datadog intakes. + +The simplest approach uses a wildcard to allow all subdomains of your Datadog site: ```conf http_port 0.0.0.0:3128 @@ -34,6 +36,22 @@ http_access allow Datadog http_access allow local manager ``` +Alternatively, if you require more granular control, you can explicitly list each Datadog endpoint instead of using a wildcard. For the full list of domains and IP ranges the Agent needs to reach, see [Network Traffic][7]. For example: + +```conf +http_port 0.0.0.0:3128 + +acl local src 127.0.0.1/32 + +acl Datadog dstdomain agent.{{< region-param key="dd_site" >}} +acl Datadog dstdomain process.{{< region-param key="dd_site" >}} +acl Datadog dstdomain logs.{{< region-param key="dd_site" >}} +acl Datadog dstdomain api.{{< region-param key="dd_site" >}} + +http_access allow Datadog +http_access allow local manager +``` + ### Start Squid Start (or restart) Squid so that your new configurations can be applied. @@ -88,12 +106,12 @@ After saving these changes, [restart the Agent][1]. {{% /tab %}} {{% tab "Operator" %}} -Modify the DatadogAgent custom resource to include the following: +Modify the DatadogAgent CR to include the following: ```yaml spec: global: - env: + proxy: http: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 https: http://squid-proxy.proxy-namespace.svc.cluster.local:3128 ``` @@ -127,3 +145,4 @@ Verify that Datadog is able to receive the data from your Agent(s) by checking y [4]: https://wiki.squid-cache.org/KnowledgeBase/Windows [5]: /agent/configuration/proxy/ [6]: /agent/configuration/agent-configuration-files#agent-configuration-directory +[7]: /agent/configuration/network/#overview From 2956d0ac30e2c52a86e15c23cea2bf21aa082ed2 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 14:55:49 -0400 Subject: [PATCH 5/8] Update content/en/agent/configuration/proxy_squid.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- content/en/agent/configuration/proxy_squid.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index fc659e98092..4efcdbc07a8 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -21,7 +21,7 @@ Install Squid on a host that has connectivity to both your internal Agents and D To configure Squid, edit the configuration file. This file is usually located at `/etc/squid/squid.conf` on Linux or `C:\squid\etc\squid.conf` in Windows. For other operating systems, see [Agent configuration directory][6]. -Edit your `squid.conf` configuration file so that Squid is able to accept local traffic and forward it to the necessary Datadog intakes. +Edit your `squid.conf` configuration file so that Squid can accept local traffic and forward it to the necessary Datadog intakes. The simplest approach uses a wildcard to allow all subdomains of your Datadog site: From 9a95254e6c21b25c1c4b665a026ffd61a3c5ef53 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 14:55:57 -0400 Subject: [PATCH 6/8] Update content/en/agent/configuration/proxy_squid.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- content/en/agent/configuration/proxy_squid.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index 4efcdbc07a8..d5879e6edf6 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -106,7 +106,7 @@ After saving these changes, [restart the Agent][1]. {{% /tab %}} {{% tab "Operator" %}} -Modify the DatadogAgent CR to include the following: +Modify the `DatadogAgent` custom resource to include the following: ```yaml spec: From 71d9f05da256bd95830ad7a7a613a2b1db338748 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 14:56:49 -0400 Subject: [PATCH 7/8] Update content/en/agent/configuration/proxy_squid.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- content/en/agent/configuration/proxy_squid.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index d5879e6edf6..3272685d8f1 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -23,7 +23,7 @@ To configure Squid, edit the configuration file. This file is usually located at Edit your `squid.conf` configuration file so that Squid can accept local traffic and forward it to the necessary Datadog intakes. -The simplest approach uses a wildcard to allow all subdomains of your Datadog site: +For most setups, a wildcard rule that allows all subdomains of your Datadog site is sufficient: ```conf http_port 0.0.0.0:3128 From b20506c0b9225b9dc66b02999c1e8dc9561c8230 Mon Sep 17 00:00:00 2001 From: Beommo Yang Date: Fri, 26 Jun 2026 15:24:14 -0400 Subject: [PATCH 8/8] Refine wording in proxy_squid.md for clarity Updated language for clarity and precision in the proxy_squid.md documentation. --- content/en/agent/configuration/proxy_squid.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/en/agent/configuration/proxy_squid.md b/content/en/agent/configuration/proxy_squid.md index 3272685d8f1..c85320a6567 100644 --- a/content/en/agent/configuration/proxy_squid.md +++ b/content/en/agent/configuration/proxy_squid.md @@ -21,9 +21,9 @@ Install Squid on a host that has connectivity to both your internal Agents and D To configure Squid, edit the configuration file. This file is usually located at `/etc/squid/squid.conf` on Linux or `C:\squid\etc\squid.conf` in Windows. For other operating systems, see [Agent configuration directory][6]. -Edit your `squid.conf` configuration file so that Squid can accept local traffic and forward it to the necessary Datadog intakes. +Edit your `squid.conf` configuration file so that Squid is able to accept local traffic and forward it to the necessary Datadog intakes. -For most setups, a wildcard rule that allows all subdomains of your Datadog site is sufficient: +The simplest approach uses a wildcard to allow all subdomains of your Datadog site: ```conf http_port 0.0.0.0:3128 @@ -38,6 +38,10 @@ http_access allow local manager Alternatively, if you require more granular control, you can explicitly list each Datadog endpoint instead of using a wildcard. For the full list of domains and IP ranges the Agent needs to reach, see [Network Traffic][7]. For example: +{{< warning >}} +The example below only includes a subset of Datadog endpoints. Make sure to include all domains required by the Datadog features you use. See [Network Traffic][7] for the complete list. +{{< /warning >}} + ```conf http_port 0.0.0.0:3128 @@ -106,7 +110,7 @@ After saving these changes, [restart the Agent][1]. {{% /tab %}} {{% tab "Operator" %}} -Modify the `DatadogAgent` custom resource to include the following: +Modify the DatadogAgent CR to include the following: ```yaml spec: