Document NO_PROXY configuration and matching rules by beommoyang · Pull Request #37802 · DataDog/documentation

beommoyang · 2026-06-26T19:28:40Z

Added section on NO_PROXY accepted values and matching rules for Agent HTTP(S) requests.

What does this PR do? What is the motivation?

Added a new NO_PROXY Accepted Values section explaining the difference between exact matching (default) and nonexact matching (no_proxy_nonexact_match: true), including matching rules for domain names, subdomains, CIDR ranges, exact IPs, and hostnames.

Merge readiness

Ready for merge

For Datadog employees:

⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Used Claude Code for research and drafting.

Additional notes

Added section on `NO_PROXY` accepted values and matching rules for Agent HTTP(S) requests.

beommoyang · 2026-06-26T19:41:09Z

/review

github-actions

🤖 Automated review by Claude. AI-generated; verify before acting.

Three style nits on the new section: heading should use sentence case, the recommendation can be more direct, and "nor" reads awkwardly without "neither".

_{Reviewed 862475cb77837f68ea870f3964c6af8676f6720a — workflow run}

github-actions · 2026-06-26T19:44:04Z


+## `NO_PROXY` Accepted Values
+
+By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.


Style: Use a direct, active voice instead of "It is recommended to". Also, the existing config example above (line 53) already uses no_proxy_nonexact_match: true and notes that it's recommended — consider whether this sentence still adds value or could be tightened.

Suggested change

By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.

By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). Datadog recommends enabling `no_proxy_nonexact_match` so the Agent matches `NO_PROXY` values using the same rules as Agent integrations.

github-actions · 2026-06-26T19:44:04Z

+The following rules apply to Agent integrations (and the whole Agent when `no_proxy_nonexact_match` is enabled):
+* A domain name matches that name and all subdomains, for example:
+  - `datadoghq.com` matches `app.agent.datadoghq.com`, `www.datadoghq.com`, `datadoghq.com`, but **not** `www.notdatadoghq.com`
+  - `datadoghq` matches `frontend.datadoghq`, `backend.datadoghq`, but **not** `www.datadoghq.com` nor `www.datadoghq.eu`


Style: "nor" without a preceding "neither" reads awkwardly; use "or" for parallelism with the other bullets.

Suggested change

- `datadoghq` matches `frontend.datadoghq`, `backend.datadoghq`, but **not** `www.datadoghq.com` nor `www.datadoghq.eu`

- `datadoghq` matches `frontend.datadoghq`, `backend.datadoghq`, but **not** `www.datadoghq.com` or `www.datadoghq.eu`

Agree with this suggestion, please update - thank you!

Expanded proxy configuration options for Kubernetes deployments, including Helm and Datadog Operator methods.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

beommoyang · 2026-06-26T20:14:16Z

/review

github-actions

🤖 Automated review by Claude. AI-generated; verify before acting.

Two minor style nits — content reads cleanly and the new Kubernetes examples are well-structured and consistent with existing patterns in the file.

_{Reviewed 72db01179de3b57fa127adb5403c71346995bb99 — workflow run}

github-actions · 2026-06-26T20:18:03Z

 ## Configure the Datadog Agent

-There are two options for configuring the Datadog Agent to use a proxy.
+There are several options for configuring the Datadog Agent to use a proxy depending on your deployment method.


Style: Add a comma before the qualifying clause for readability.

Suggested change

There are several options for configuring the Datadog Agent to use a proxy depending on your deployment method.

There are several options for configuring the Datadog Agent to use a proxy, depending on your deployment method.

github-actions · 2026-06-26T20:18:03Z

+
+## `NO_PROXY` accepted values
+
+By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.


Style: Prefer active voice — this matches the existing phrasing later in the file ("Datadog recommends using an HTTP proxy like Squid").

Suggested change

By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.

By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). Datadog recommends enabling `no_proxy_nonexact_match` so the Agent matches `NO_PROXY` values with the same rules used for Agent integrations.

jeff-morgan-dd

Thank you for this PR! Please see a couple of non-blocking recommended style guide edits.

jeff-morgan-dd · 2026-06-26T20:57:13Z

+
+## `NO_PROXY` accepted values
+
+By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.


Suggested change

By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.

By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). Datadog recommends enabling `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.

jeff-morgan-dd · 2026-06-26T20:58:39Z

+The following rules apply to Agent integrations (and the whole Agent when `no_proxy_nonexact_match` is enabled):
+* A domain name matches that name and all subdomains, for example:
+  - `datadoghq.com` matches `app.agent.datadoghq.com`, `www.datadoghq.com`, `datadoghq.com`, but **not** `www.notdatadoghq.com`
+  - `datadoghq` matches `frontend.datadoghq`, `backend.datadoghq`, but **not** `www.datadoghq.com` nor `www.datadoghq.eu`


Agree with this suggestion, please update - thank you!

Document NO_PROXY configuration and matching rules

e2a0339

Added section on `NO_PROXY` accepted values and matching rules for Agent HTTP(S) requests.

beommoyang requested a review from a team as a code owner June 26, 2026 19:28

Merge branch 'master' into beommo.yang-add-no-proxy-description

862475c

github-actions Bot reviewed Jun 26, 2026

View reviewed changes

beommoyang and others added 2 commits June 26, 2026 16:09

Enhance proxy configuration documentation for Kubernetes

5b92619

Expanded proxy configuration options for Kubernetes deployments, including Helm and Datadog Operator methods.

Update content/en/agent/configuration/proxy.md

72db011

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

github-actions Bot reviewed Jun 26, 2026

View reviewed changes

Merge branch 'master' into beommo.yang-add-no-proxy-description

6ba366a

jeff-morgan-dd self-assigned this Jun 26, 2026

jeff-morgan-dd approved these changes Jun 26, 2026

View reviewed changes


		## `NO_PROXY` Accepted Values

		By default, `no_proxy`/`NO_PROXY` must match endpoints exactly for Agent HTTP(S) requests (except requests performed by Agent integrations). It is recommended to enable `no_proxy_nonexact_match` to make the Agent match `NO_PROXY` values with the same rules used for Agent integrations.

	- `datadoghq` matches `frontend.datadoghq`, `backend.datadoghq`, but not `www.datadoghq.com` nor `www.datadoghq.eu`
	- `datadoghq` matches `frontend.datadoghq`, `backend.datadoghq`, but not `www.datadoghq.com` or `www.datadoghq.eu`

	There are several options for configuring the Datadog Agent to use a proxy depending on your deployment method.
	There are several options for configuring the Datadog Agent to use a proxy, depending on your deployment method.

Uh oh!

Conversation

beommoyang commented Jun 26, 2026

What does this PR do? What is the motivation?

Merge readiness

For Datadog employees:

AI assistance

Additional notes

Uh oh!

beommoyang commented Jun 26, 2026

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

jeff-morgan-dd Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

beommoyang commented Jun 26, 2026

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

jeff-morgan-dd left a comment

Choose a reason for hiding this comment

Uh oh!

jeff-morgan-dd Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

jeff-morgan-dd Jun 26, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants