Add validation to process agent config endpoint

[daniel-taf]

What does this PR do?

Motivation

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=51458289 --os-family=ubuntu

Note: This applies to commit 5519fbf

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 26052f9b0fdb75103002f7090cab64a7c9a12aa2

Diff per package

package	diff	status	size	ancestor	threshold
datadog-heroku-agent-amd64-deb	0.01MB	⚠️	505.05MB	505.04MB	70.00MB
datadog-iot-agent-x86_64-rpm	0.01MB	⚠️	113.38MB	113.37MB	10.00MB
datadog-iot-agent-x86_64-suse	0.01MB	⚠️	113.38MB	113.37MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.01MB	⚠️	108.84MB	108.84MB	10.00MB
datadog-iot-agent-amd64-deb	0.01MB	⚠️	113.31MB	113.30MB	10.00MB
datadog-iot-agent-arm64-deb	0.01MB	⚠️	108.78MB	108.77MB	10.00MB
datadog-agent-aarch64-rpm	0.00MB	⚠️	942.98MB	942.98MB	140.00MB
datadog-agent-arm64-deb	0.00MB	✅	933.77MB	933.77MB	140.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.58MB	78.58MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.65MB	78.65MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.65MB	78.65MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.78MB	55.78MB	10.00MB
datadog-agent-amd64-deb	-0.03MB	✅	1187.74MB	1187.76MB	140.00MB
datadog-agent-x86_64-rpm	-0.03MB	✅	1196.97MB	1197.00MB	140.00MB
datadog-agent-x86_64-suse	-0.03MB	✅	1196.97MB	1197.00MB	140.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: e3f5dac2-3a3a-4248-a39d-3b14421ec700

Baseline: 26052f9
Comparison: 5519fbf
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+1.22	[+0.49, +1.95]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+1.03	[+0.34, +1.73]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.56	[+0.48, +0.65]	1	Logs
➖	quality_gate_idle	memory utilization	+0.27	[+0.24, +0.31]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.06	[-0.79, +0.92]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.04	[-0.72, +0.80]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.03	[-0.86, +0.92]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.02	[-0.84, +0.89]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.00	[-0.79, +0.79]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.02	[-0.12, +0.09]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.03	[-0.80, +0.75]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.05	[-0.69, +0.58]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.19	[-0.66, +0.27]	1	Logs
➖	file_tree	memory utilization	-0.35	[-0.48, -0.22]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.94	[-1.07, -0.82]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-2.81	[-5.67, +0.04]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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 memory_usage: 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 lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.