test

[andrewqian2001datadog]

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

[agent-platform-auto-pr]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 004ef89

Successful checks

Info

	Quality gate	Delta	On disk size (MiB)	Delta	On wire size (MiB)
✅	agent_deb_amd64	$${+0.02}$$	$${706.33}$$ < $${707.13}$$	$${-0.04}$$	$${173.27}$$ < $${174.16}$$
✅	agent_deb_amd64_fips	$${+0.01}$$	$${702.55}$$ < $${702.86}$$	$${+0}$$	$${172.58}$$ < $${173.5}$$
✅	agent_heroku_amd64	$${+0}$$	$${327.51}$$ < $${327.92}$$	$${-0}$$	$${87.23}$$ < $${88.21}$$
✅	agent_msi	$${+0}$$	$${570.42}$$ < $${982.08}$$	$${-0.02}$$	$${142.48}$$ < $${143.49}$$
✅	agent_rpm_amd64	$${+0.02}$$	$${706.32}$$ < $${707.12}$$	$${+0.09}$$	$${176.44}$$ < $${177.29}$$
✅	agent_rpm_amd64_fips	$${+0.01}$$	$${702.53}$$ < $${702.85}$$	$${+0}$$	$${175.4}$$ < $${176.32}$$
✅	agent_rpm_arm64	$${+0.01}$$	$${688.02}$$ < $${691.67}$$	$${+0.01}$$	$${159.42}$$ < $${160.7}$$
✅	agent_rpm_arm64_fips	$${+0.01}$$	$${685.06}$$ < $${687.54}$$	$${+0.01}$$	$${159.17}$$ < $${160.11}$$
✅	agent_suse_amd64	$${+0.02}$$	$${706.32}$$ < $${707.12}$$	$${+0.09}$$	$${176.44}$$ < $${177.29}$$
✅	agent_suse_amd64_fips	$${+0.01}$$	$${702.53}$$ < $${702.85}$$	$${+0}$$	$${175.4}$$ < $${176.32}$$
✅	agent_suse_arm64	$${+0.01}$$	$${688.02}$$ < $${691.67}$$	$${+0.01}$$	$${159.42}$$ < $${160.7}$$
✅	agent_suse_arm64_fips	$${+0.01}$$	$${685.06}$$ < $${687.54}$$	$${+0.01}$$	$${159.17}$$ < $${160.11}$$
✅	docker_agent_amd64	$${+0.02}$$	$${768.57}$$ < $${769.38}$$	$${+0}$$	$${261.17}$$ < $${262.06}$$
✅	docker_agent_arm64	$${+0.01}$$	$${774.81}$$ < $${778.35}$$	$${+0}$$	$${250.27}$$ < $${251.72}$$
✅	docker_agent_jmx_amd64	$${+0.02}$$	$${959.45}$$ < $${960.26}$$	$${+0.01}$$	$${329.81}$$ < $${330.69}$$
✅	docker_agent_jmx_arm64	$${+0.01}$$	$${954.41}$$ < $${957.95}$$	$${-0}$$	$${314.89}$$ < $${316.35}$$
✅	docker_cluster_agent_amd64	$${+0}$$	$${179.41}$$ < $${179.56}$$	$${+0}$$	$${63.44}$$ < $${64.14}$$
✅	docker_cluster_agent_arm64	$${+0}$$	$${195.36}$$ < $${196.79}$$	$${+0.01}$$	$${59.75}$$ < $${60.69}$$
✅	docker_cws_instrumentation_amd64	$${0}$$	$${7.13}$$ < $${7.18}$$	$${-0}$$	$${2.99}$$ < $${3.33}$$
✅	docker_cws_instrumentation_arm64	$${0}$$	$${6.69}$$ < $${6.92}$$	$${-0}$$	$${2.73}$$ < $${3.09}$$
✅	docker_dogstatsd_amd64	$${+0}$$	$${38.75}$$ < $${39.38}$$	$${-0}$$	$${15.0}$$ < $${15.82}$$
✅	docker_dogstatsd_arm64	$${0}$$	$${37.06}$$ < $${37.94}$$	$${+0}$$	$${14.33}$$ < $${14.83}$$
✅	dogstatsd_deb_amd64	$${0}$$	$${29.97}$$ < $${30.61}$$	$${-0}$$	$${7.93}$$ < $${8.79}$$
✅	dogstatsd_deb_arm64	$${0}$$	$${28.13}$$ < $${29.11}$$	$${-0}$$	$${6.81}$$ < $${7.71}$$
✅	dogstatsd_rpm_amd64	$${0}$$	$${29.97}$$ < $${30.61}$$	$${+0}$$	$${7.94}$$ < $${8.8}$$
✅	dogstatsd_suse_amd64	$${0}$$	$${29.97}$$ < $${30.61}$$	$${+0}$$	$${7.94}$$ < $${8.8}$$
✅	iot_agent_deb_amd64	$${0}$$	$${42.73}$$ < $${43.29}$$	$${+0}$$	$${11.19}$$ < $${12.04}$$
✅	iot_agent_deb_arm64	$${0}$$	$${39.87}$$ < $${40.92}$$	$${-0}$$	$${9.57}$$ < $${10.45}$$
✅	iot_agent_deb_armhf	$${+0}$$	$${40.44}$$ < $${41.03}$$	$${+0}$$	$${9.76}$$ < $${10.62}$$
✅	iot_agent_rpm_amd64	$${0}$$	$${42.73}$$ < $${43.29}$$	$${-0}$$	$${11.2}$$ < $${12.06}$$
✅	iot_agent_suse_amd64	$${0}$$	$${42.73}$$ < $${43.29}$$	$${-0}$$	$${11.2}$$ < $${12.06}$$

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: d1372bc7-f223-4bd5-8ade-e8fb694ca262

Baseline: d1bd251
Comparison: 81985c9
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
❌	docker_containers_cpu	% cpu utilization	+5.21	[+2.14, +8.27]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
❌	docker_containers_cpu	% cpu utilization	+5.21	[+2.14, +8.27]	1	Logs
➖	quality_gate_logs	% cpu utilization	+1.39	[-0.12, +2.89]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.44	[+0.39, +0.49]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	+0.37	[+0.14, +0.60]	1	Logs
➖	file_tree	memory utilization	+0.27	[+0.21, +0.33]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	+0.17	[+0.01, +0.32]	1	Logs
➖	ddot_logs	memory utilization	+0.15	[+0.10, +0.21]	1	Logs
➖	quality_gate_idle	memory utilization	+0.12	[+0.08, +0.16]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	+0.12	[+0.08, +0.15]	1	Logs bounds checks dashboard
➖	file_to_blackhole_100ms_latency	egress throughput	+0.07	[+0.03, +0.12]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.07, +0.07]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.00	[-0.12, +0.12]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.13, +0.11]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.02	[-0.39, +0.35]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.04	[-0.46, +0.38]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.05	[-0.46, +0.36]	1	Logs
➖	docker_containers_memory	memory utilization	-0.07	[-0.14, +0.01]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.12	[-0.22, -0.03]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.22	[-0.40, -0.04]	1	Logs
➖	otlp_ingest_metrics	memory utilization	-0.24	[-0.40, -0.09]	1	Logs
➖	ddot_metrics	memory utilization	-0.69	[-0.91, -0.48]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.40	[-1.47, -1.33]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-1.92	[-2.13, -1.70]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	lost_bytes	10/10
✅	file_to_blackhole_1000ms_latency	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_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	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".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Profiling Replicate Execution Failures (ddprof)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
docker_containers_memory	comparison	10	Crashed (exit code: 0)	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates 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_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_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, 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_idle, 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 memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.