[ADP] gate data_plane.enabled to Linux at config load time#50151
Conversation
ADP is a Linux-only component. Rather than letting each downstream consumer silently ignore the flag on non-Linux, reset data_plane.enabled to false (with a warning) in sanitizeDataPlaneConfig, called from LoadDatadog, so all consumers automatically see the correct value regardless of platform. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
- Add GetSource assertion to TestSanitizeDataPlaneConfigNonLinux to verify the override is applied at SourceAgentRuntime precedence level - Replace raw string "data_plane.enabled" with DataPlaneEnabled constant in sanitizeDataPlaneConfig function for consistency and DRY principle Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
data_plane.enabled to Linux at config load time
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 84e5eac814
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Without this, a fleet policy (SourceFleetPolicies) applied after LoadDatadog could set data_plane.enabled=true and bypass the gate, since SourceAgentRuntime was only written when the value was already true at sanitize time. Now the override is always written on non-Linux so SourceFleetPolicies (lower priority) can never win. The warning is still only emitted when the value was actually true at call time. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
|
🎯 Code Coverage (details) 🔗 Commit SHA: 03e8787 | Docs | Datadog PR Page | Give us feedback! |
Files inventory check summaryFile checks results against ancestor a0db807d: Results for datadog-agent_7.80.0~devel.git.342.03e8787.pipeline.110609259-1_amd64.deb:No change detected |
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
22 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 7d29ffb Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -0.10 | [-3.10, +2.90] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | quality_gate_logs | % cpu utilization | +1.05 | [+0.07, +2.03] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | +0.64 | [+0.49, +0.79] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | +0.58 | [+0.42, +0.74] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.57 | [+0.52, +0.61] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | +0.31 | [+0.21, +0.41] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.25 | [+0.20, +0.30] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics | memory utilization | +0.25 | [+0.05, +0.44] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | +0.22 | [+0.12, +0.32] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.21 | [+0.02, +0.39] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.00 | [-0.20, +0.19] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.10, +0.09] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.13, +0.11] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.21, +0.19] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.02 | [-0.06, +0.02] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.04 | [-0.46, +0.39] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.04 | [-0.44, +0.36] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.06 | [-0.60, +0.47] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | -0.10 | [-3.10, +2.90] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | -0.19 | [-0.44, +0.06] | 1 | Logs bounds checks dashboard |
| ➖ | file_tree | memory utilization | -0.23 | [-0.28, -0.18] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.28 | [-0.35, -0.21] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.29 | [-0.53, -0.05] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.41 | [-0.60, -0.22] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | observed_value | links |
|---|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | 700 ≥ 26 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | 252.25MiB ≤ 370MiB | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | 700 ≥ 26 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | 0.16GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_0ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | 0.21GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_1000ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | 0.18GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_100ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | 0.19GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_500ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | 3 ≤ 4 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | 143.01MiB ≤ 147MiB | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | 3 ≤ 4 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | 467.40MiB ≤ 495MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | 4 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | 176.24MiB ≤ 195MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | 341.62 ≤ 2000 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | 3 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | 380.95MiB ≤ 430MiB | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
b27860f
into
main
## Summary Follows up on #50151. Adds `DD_DATA_PLANE_FORCE_ENABLE=true` as a developer escape hatch for the non-Linux OS gate in `sanitizeDataPlaneConfig`. ## Test plan - [x] `dda inv test --targets=./pkg/config/setup/...` passes (295 tests, including 4 new bypass cases) - [x] Verify on macOS: set `DD_DATA_PLANE_FORCE_ENABLE=true` in `datadog.yaml` env and confirm `data_plane.enabled` is honoured 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: jesse.szwedko <[email protected]>
Summary
ADP (Agent Data Plane) is Linux-only, but
data_plane.enabled: truewas silently ignored on Windows and macOS with no feedback to the user. This PR adds a platform gate in the config loading path that emits a warning and resetsdata_plane.enabledto false on non-Linux platforms, ensuring every downstream consumer (dogstatsd ADP path, OTLP proxy) automatically sees the correct value without per-site guards.Follows up on review feedback from #49891.
No changelog entry since ADP still is a "hidden feature".
Test plan
dda inv test --targets=./pkg/config/setup/...passes (291 tests)🤖 Generated with Claude Code