Re-enable config streaming by default

[rahulkaukuntla]

What does this PR do?

Re-enables config streaming by default (remote_agent.configstream.consumer.enabled: false -> true). This is the un-revert of #55817 only, out of the three commits reverted together in #55851.

Motivation

#55851 reverted config streaming after incident 60263: DD_RUNTIME_SECURITY_CONFIG_ENABLED was set only on the security-agent container, the consumer's env-layer wipe discarded it, the core Agent streamed the default false, and the security-agent crash-looped with ErrAllComponentsDisabled. The rest of this stack gives per-remote-agent settings a home on the core Agent so that class of failure cannot recur; this commit turns streaming back on.

Describe how you validated your changes

dda inv tidy, linter.go (0 issues) and dda inv test green on the assembled stack, across both the main and test/new-e2e modules. Live test with a locally built core agent plus trace-, process- and security-agent: streaming happened with no explicit remote_agent.configstream.consumer.enabled anywhere in the config file.

Additional Notes

Deliberately does not un-revert #55844 — network_config.direct_send stays false. The OTLP span-name fix from #55853, also caught in that revert, is restored one branch down instead.

Stack, merge bottom-up: configstream/per-agent-config-keys <- configstream/consumer-override-remap <- configstream/deprecate-remote-env <- configstream/e2e-core-agent-env <- configstream/enable-by-default (this PR).

[datadog-datadog-us1-prod]

🎯 Code Coverage (details)
• Patch Coverage: 38.91%
• Overall Coverage: 55.31% (+0.01%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 53c8c28 | Docs | View more details | Give us feedback!}

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor cbbd916
📊 Static Quality Gates Dashboard
🔗 SQG Job
SOME SIZE DELTAS ARE N/A (ANCESTOR METRICS NOT YET AVAILABLE). RETRY JOB

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	N/A	N/A → 768.590 → 771.220
✅	agent_deb_amd64_fips	N/A	N/A → 715.167 → 718.020
✅	agent_heroku_amd64	N/A	N/A → 316.156 → 322.460
✅	agent_msi	N/A	N/A → 647.872 → 662.360
✅	agent_rpm_amd64	N/A	N/A → 768.574 → 771.190
✅	agent_rpm_amd64_fips	N/A	N/A → 715.150 → 718.020
✅	agent_rpm_arm64	N/A	N/A → 740.491 → 744.370
✅	agent_rpm_arm64_fips	N/A	N/A → 691.624 → 695.880
✅	agent_suse_amd64	N/A	N/A → 768.574 → 771.190
✅	agent_suse_amd64_fips	N/A	N/A → 715.150 → 718.020
✅	agent_suse_arm64	N/A	N/A → 740.491 → 744.370
✅	agent_suse_arm64_fips	N/A	N/A → 691.624 → 695.880
✅	docker_agent_amd64	N/A	N/A → 827.554 → 828.420
✅	docker_agent_arm64	N/A	N/A → 824.527 → 828.440
✅	docker_agent_jmx_amd64	N/A	N/A → 1018.466 → 1019.630
✅	docker_agent_jmx_arm64	N/A	N/A → 1004.219 → 1008.130
✅	docker_cluster_agent_amd64	N/A	N/A → 212.687 → 213.660
✅	docker_cluster_agent_arm64	N/A	N/A → 225.718 → 226.660
✅	docker_cws_instrumentation_amd64	N/A	N/A → 7.439 → 8.400
✅	docker_cws_instrumentation_arm64	N/A	N/A → 6.877 → 7.110
✅	docker_dogstatsd_amd64	N/A	N/A → 39.561 → 40.440
✅	docker_dogstatsd_arm64	N/A	N/A → 37.623 → 38.580
✅	docker_host_profiler_amd64	N/A	N/A → 307.576 → 319.480
✅	docker_host_profiler_arm64	N/A	N/A → 318.792 → 330.690
✅	dogstatsd_deb_amd64	N/A	N/A → 30.303 → 31.220
✅	dogstatsd_deb_arm64	N/A	N/A → 28.315 → 29.590
✅	dogstatsd_rpm_amd64	N/A	N/A → 30.303 → 31.220
✅	dogstatsd_suse_amd64	N/A	N/A → 30.303 → 31.220
✅	iot_agent_deb_amd64	N/A	N/A → 46.651 → 47.550
✅	iot_agent_deb_arm64	N/A	N/A → 43.280 → 44.220
✅	iot_agent_deb_armhf	N/A	N/A → 44.098 → 45.020
✅	iot_agent_rpm_amd64	N/A	N/A → 46.652 → 47.550
✅	iot_agent_suse_amd64	N/A	N/A → 46.651 → 47.550

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: ea6eb7cc-4337-4f21-b796-2df865f2e5ad

Baseline: cbbd916
Comparison: 53c8c28
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+2.30	[+1.43, +3.16]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	+0.90	[+0.87, +0.93]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	+0.60	[+0.36, +0.85]	1	Logs
➖	quality_gate_security_no_fs_load	memory utilization	+0.44	[+0.37, +0.51]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.24	[+0.20, +0.28]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	+0.04	[+0.00, +0.08]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	-0.03	[-0.24, +0.18]	1	Logs
➖	quality_gate_idle	memory utilization	-0.04	[-0.08, +0.00]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	-0.46	[-0.58, -0.33]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.51	[-0.74, -0.28]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	4 ≤ 5	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	175.19MiB ≤ 179MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	746.88KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	4 ≤ 5	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	532.18MiB ≤ 537MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.15MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	21 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	213.16MiB ≤ 228MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.42MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	374.04 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	19 ≤ 40	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	425.82MiB ≤ 455MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.94GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_private_action_runner	memory_usage	10/10	72.12MiB ≤ 75MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	29.30 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	329.02MiB ≤ 355MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	62.83 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	303.81MiB ≤ 335MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	22.61 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	311.99MiB ≤ 345MiB	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:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. 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.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_private_action_runner, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_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 missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, 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, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.