Expose DPA mode and resource metrics

[clamoriniere]

What does this PR do?

Adds two Cluster Agent workload autoscaling metrics for DatadogPodAutoscaler visibility.

• datadog.cluster_agent.autoscaling.workload.apply_mode

  • Value: 1
  • Tags: base tags, dpa_mode, dpa_dimension
  • dpa_mode is apply or preview
  • dpa_dimension is emitted for each enabled autoscaling dimension: horizontal, vertical, or both

• datadog.cluster_agent.autoscaling.workload.vertical_scaling.controlled_resources

  • Value: 1
  • Tags: base tags, kube_container_name, resource_name
  • Emits one point per resource controlled by vertical autoscaling for a container
  • Uses kube_container_name:all for wildcard or default container constraints
  • Defaults to resource_name:cpu and resource_name:memory when controlledResources is omitted, including unconstrained vertical DPAs

Motivation

Dashboards need to identify DPA preview/apply mode by autoscaling dimension and show which container resources are vertically autoscaled for one container or all containers.

Describe how you validated your changes

• Ran GOENV_VERSION=1.26.3 gofmt -w pkg/clusteragent/autoscaling/workload/metrics/generator.go pkg/clusteragent/autoscaling/workload/metrics/generator_test.go because the repo-pinned Go 1.26.6 is not installed in this environment.
• Ran git diff --check.
• Local bazel run //:gazelle -- -mode=diff and dda inv test --targets=./pkg/clusteragent/autoscaling/workload/metrics could not complete because Bazel failed fetching the external GCC toolchain through the proxy (502 Bad Gateway).

Additional Notes

N/A

---

PR by Bits - View session in Datadog: https://app.datadoghq.com/code/0a0a94e2-629f-4089-af07-4fe2b56d2cac

Comment @DataDog to request changes

[datadog-datadog-prod-us1]

View session in Datadog

Bits Code status: ✅ Done

CI Auto-fix: Disabled | Enable

Comment @DataDog to request changes

[datadog-datadog-prod-us1-2]

I can only run on private repositories.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6f83b01293

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 93.10%
• Overall Coverage: 52.63% (+0.01%)

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

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 0a9c0176:

Results for datadog-agent_7.84.0~devel.git.491.303a68e.pipeline.133604941-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.84.0~devel.git.491.303a68e.pipeline.133604941-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 0a9c017
📊 Static Quality Gates Dashboard
🔗 SQG Job

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	docker_agent_amd64	-18.9 KiB (0.00% reduction, +5.66% of buffer)	819.814 → 819.796 → 820.140
✅	docker_agent_arm64	-19.0 KiB (0.00% reduction, +17.75% of buffer)	820.785 → 820.767 → 820.890
✅	docker_agent_jmx_amd64	-18.9 KiB (0.00% reduction, +10.63% of buffer)	1010.726 → 1010.708 → 1010.900
✅	docker_agent_jmx_arm64	-19.0 KiB (0.00% reduction, +20.09% of buffer)	1000.478 → 1000.459 → 1000.570
✅	docker_cluster_agent_amd64	+4.0 KiB (0.00% increase, -0.57% of buffer)	211.439 → 211.443 → 212.130
✅	docker_cluster_agent_arm64	+64.0 KiB (0.03% increase, -8.95% of buffer)	224.521 → 224.584 → 225.220
✅	docker_host_profiler_amd64	-38.42 KiB (0.01% reduction, +0.35% of buffer)	306.845 → 306.808 → 317.700
✅	docker_host_profiler_arm64	-38.43 KiB (0.01% reduction, +0.35% of buffer)	318.177 → 318.139 → 328.970

25 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	761.235 MiB
✅	agent_deb_amd64_fips	713.990 MiB
✅	agent_heroku_amd64	312.906 MiB
✅	agent_msi	647.884 MiB
✅	agent_rpm_amd64	761.219 MiB
✅	agent_rpm_amd64_fips	713.974 MiB
✅	agent_rpm_arm64	737.112 MiB
✅	agent_rpm_arm64_fips	693.146 MiB
✅	agent_suse_amd64	761.219 MiB
✅	agent_suse_amd64_fips	713.974 MiB
✅	agent_suse_arm64	737.112 MiB
✅	agent_suse_arm64_fips	693.146 MiB
✅	docker_cws_instrumentation_amd64	7.443 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.529 MiB
✅	docker_dogstatsd_arm64	37.623 MiB
✅	dogstatsd_deb_amd64	30.267 MiB
✅	dogstatsd_deb_arm64	28.283 MiB
✅	dogstatsd_rpm_amd64	30.267 MiB
✅	dogstatsd_suse_amd64	30.267 MiB
✅	iot_agent_deb_amd64	46.540 MiB
✅	iot_agent_deb_arm64	43.177 MiB
✅	iot_agent_deb_armhf	43.983 MiB
✅	iot_agent_rpm_amd64	46.541 MiB
✅	iot_agent_suse_amd64	46.540 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: a044e1fb-95a3-4dfe-b728-505bc237223d

Baseline: 0a9c017
Comparison: 303a68e
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_private_action_runner	memory utilization	+0.31	[+0.19, +0.43]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.08	[+0.05, +0.12]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	+0.02	[-0.19, +0.24]	1	Logs
➖	quality_gate_security_no_fs_load	memory utilization	-0.01	[-0.10, +0.07]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.13	[-0.17, -0.09]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.20	[-0.25, -0.15]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.42	[-0.65, -0.19]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.43	[-0.46, -0.39]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	-0.90	[-1.13, -0.66]	1	Logs
➖	quality_gate_logs	% cpu utilization	-1.99	[-2.84, -1.14]	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 = 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	172.12MiB ≤ 178MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	749.83KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	4 = 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	515.27MiB ≤ 538MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.14MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	18 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	211.03MiB ≤ 229MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.39MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	364.91 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	22 ≤ 40	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	423.68MiB ≤ 453MiB	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.01MiB ≤ 76MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	28.42 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	322.10MiB ≤ 335MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	61.36 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	302.60MiB ≤ 314MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	22.46 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	311.42MiB ≤ 343MiB	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_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate 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_private_action_runner, 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_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 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_logs, bounds check total_bytes_received: 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_metrics_logs, bounds check memory_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 total_bytes_received: 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 cpu_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_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.