Report Remote Configuration and workload autoscaling in the Cluster Agent status

[clamoriniere]

What does this PR do?

Reports Remote Configuration and workload autoscaling health in datadog-cluster-agent status.

Every Remote Configuration client is listed, with the endpoint it polls:

Remote Configuration
====================

Endpoint: https://config.datadoghq.com.
Organization enabled: True
API Key: Authorized
Last error: None

Additional clients
------------------
  - autoscaling
      Endpoint: https://config.datacat.com
      Organization enabled: True
      API Key: Authorized
      Last error: None

And a new Autoscaling section reports what workload autoscaling is receiving:

Autoscaling
===========

  Workload
  --------
  DatadogPodAutoscalers: 2
  Leader: true
  Remote Config connection: Receiving updates
  Remote Config client: autoscaling

  CONTAINER_AUTOSCALING_SETTINGS
    Last config version: 2
    Last update: 2026-08-28T22:59:53Z (5m56s ago)
    Configs in last update: 1
    Updates received: 1

  CONTAINER_AUTOSCALING_VALUES
    Last config version: 41
    Last update: 2026-08-28T23:05:48Z (1s ago)
    Configs in last update: 1
    Updates received: 7

Both samples are taken from a Cluster Agent whose autoscaling client targets a different Remote Configuration backend than its default client, with the extra endpoint anonymized.

Motivation

Per-instance Remote Configuration status was exported but never rendered, so a Cluster Agent with additional clients gave no sign they existed and a failing one was invisible to status.

Separately, there was no way to tell whether workload autoscaling was receiving anything over Remote Configuration, which is the first question asked when an autoscaler is not behaving.

Describe how you validated your changes

Unit tests over the text, JSON and HTML renderings, including an unauthorized extra client, the default client not being listed twice, and the three workload autoscaling states (disabled, enabled but not started, running).

Also validated end to end on a local kind cluster: both sections rendered as shown above against live configuration arriving from a second backend.

Additional Notes

Also fixes a missing trailing newline in the secrets status template. It ended with {{- end -}}, which swallowed the file's last newline, so any section rendered after it landed flush against its header. This was latent because secrets was previously the last section.

Stacked on #55618, which adds the additional clients this reports on.

🤖 PR description and code assisted by Claude:claude-opus-5

[github-actions]

AI review by Codex (OpenAI) - workflow run

Patch is incorrect: workload autoscaling status can retain stale version and error information after newer Remote Configuration updates.

[github-actions]

AI review by Codex (OpenAI) - workflow run

patch is correct — the status reporting, synchronization, rendering, and tests are consistent with the intended behavior.

[datadog-datadog-prod-us1]

More details

The static review found no reportable defect. The status output handles disabled, not-started, and active workload autoscaling states, and it lists extra Remote Configuration clients.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 62e66bf · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 88.68%
• Overall Coverage: 52.74% (+0.00%)

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

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor eb7754dc:

Results for datadog-agent_7.84.0~devel.git.596.c83527a.pipeline.134080488-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.84.0~devel.git.596.c83527a.pipeline.134080488-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 eb7754d
📊 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 → 761.733 → 764.840
✅	agent_deb_amd64_fips	N/A	N/A → 713.987 → 716.080
✅	agent_heroku_amd64	N/A	N/A → 312.990 → 319.080
✅	agent_msi	N/A	N/A → 648.399 → 661.050
✅	agent_rpm_amd64	N/A	N/A → 761.717 → 764.810
✅	agent_rpm_amd64_fips	N/A	N/A → 713.970 → 716.080
✅	agent_rpm_arm64	N/A	N/A → 737.595 → 738.310
✅	agent_rpm_arm64_fips	N/A	N/A → 693.197 → 694.350
✅	agent_suse_amd64	N/A	N/A → 761.717 → 764.810
✅	agent_suse_amd64_fips	N/A	N/A → 713.970 → 716.080
✅	agent_suse_arm64	N/A	N/A → 737.595 → 738.310
✅	agent_suse_arm64_fips	N/A	N/A → 693.197 → 694.350
✅	docker_agent_amd64	N/A	N/A → 820.742 → 821.000
✅	docker_agent_arm64	N/A	N/A → 821.663 → 821.980
✅	docker_agent_jmx_amd64	N/A	N/A → 1011.654 → 1011.910
✅	docker_agent_jmx_arm64	N/A	N/A → 1001.355 → 1001.680
✅	docker_cluster_agent_amd64	N/A	N/A → 211.316 → 212.130
✅	docker_cluster_agent_arm64	N/A	N/A → 224.461 → 225.220
✅	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.553 → 40.440
✅	docker_dogstatsd_arm64	N/A	N/A → 37.623 → 38.580
✅	docker_host_profiler_amd64	N/A	N/A → 306.870 → 317.700
✅	docker_host_profiler_arm64	N/A	N/A → 318.168 → 328.970
✅	dogstatsd_deb_amd64	N/A	N/A → 30.290 → 31.210
✅	dogstatsd_deb_arm64	N/A	N/A → 28.306 → 29.590
✅	dogstatsd_rpm_amd64	N/A	N/A → 30.290 → 31.210
✅	dogstatsd_suse_amd64	N/A	N/A → 30.290 → 31.210
✅	iot_agent_deb_amd64	N/A	N/A → 46.579 → 47.550
✅	iot_agent_deb_arm64	N/A	N/A → 43.212 → 44.220
✅	iot_agent_deb_armhf	N/A	N/A → 44.022 → 45.020
✅	iot_agent_rpm_amd64	N/A	N/A → 46.580 → 47.550
✅	iot_agent_suse_amd64	N/A	N/A → 46.579 → 47.550

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: d807eebd-60bc-4886-9874-f96fa180f309

Baseline: eb7754d
Comparison: c83527a
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_security_idle	memory utilization	+0.08	[+0.03, +0.13]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.02	[-0.07, +0.02]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.03	[-0.07, +0.00]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	-0.07	[-0.19, +0.06]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	-0.12	[-0.15, -0.08]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	-0.41	[-0.49, -0.32]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	-0.65	[-0.89, -0.40]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.86	[-1.10, -0.62]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	-0.96	[-1.17, -0.75]	1	Logs
➖	quality_gate_logs	% cpu utilization	-2.29	[-3.15, -1.44]	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.78MiB ≤ 179MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	749.69KiB ≤ 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.85MiB ≤ 537MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.13MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	20 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	213.26MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.51MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	417.36 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	20 ≤ 40	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	419.43MiB ≤ 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.06MiB ≤ 75MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	28.89 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	326.99MiB ≤ 355MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	62.13 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	301.06MiB ≤ 335MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	22.54 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	311.04MiB ≤ 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_private_action_runner, 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_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_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_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 intake_connections: 10/10 replicas passed. Gate 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_security_mean_fs_load, 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_idle, bounds check intake_connections: 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 memory_usage: 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_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.