Skip to content

dogstatsd_non_local_traffic is true by default #33018

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 24, 2025
Merged

dogstatsd_non_local_traffic is true by default #33018

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
271c0dd
`dogstatsd_non_local_traffic` is true by default
kteixeiradd Nov 24, 2025
1555a8e
Update content/en/tracing/metrics/runtime_metrics/_index.md
estherk15 Nov 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/tracing/metrics/runtime_metrics/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ Enable [DogStatsD for the Agent][2]. By default, the Datadog Agent is configured

When running the Agent in containerized environments, additional configuration is required:

1. Set `dogstatsd_non_local_traffic: true` in your main [`datadog.yaml` configuration file][8], or set the [environment variable][3] `DD_DOGSTATSD_NON_LOCAL_TRAFFIC=true`.
1. Set `dogstatsd_non_local_traffic: true` in your main [`datadog.yaml` configuration file][8], or set the [environment variable][3] `DD_DOGSTATSD_NON_LOCAL_TRAFFIC=true`. **Note**: DogStatsD non‑local traffic is enabled by default, so you only need to set this if you've overridden it.
2. Follow these container-specific setup instructions:

{{< partial name="apm/apm-runtime-metrics-containers.html" >}}
Expand Down
Loading