test(new-e2e): declare Discovery Compose embed inputs

[martavicentenavarro]

What does this PR do?

Declares the four Config Files Discovery Docker Compose fixtures in the shared Discovery E2E Bazel target's data and embedsrcs attributes.

Motivation

The fixtures are consumed through //go:embed. Declaring them makes the Bazel target's inputs explicit and hermetic for Kafka, PostgreSQL, Redis, and Spark.

Validation

• bazel run //bazel/buildifier
• bazel test //bazel/buildifier:test
• git diff --check

Additional notes

This is a stacked PR and depends on #55877, which introduces the Spark Compose fixture. It must be merged only after #55877 is merged.

[martavicentenavarro]

@codex

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-04T13:18:08.765091Z	33283f6	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-official]

More details

Each file in the four //go:embed directives now appears in both Bazel input lists. The change has no reportable correctness defect.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 33283f6365

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 55.30% (-1.64%)

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

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 7d781729:

Results for datadog-agent_7.85.0~devel.git.9.b1708b2.pipeline.135502063-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.85.0~devel.git.9.b1708b2.pipeline.135502063-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 7d78172
📊 Static Quality Gates Dashboard
🔗 SQG Job

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+8.89 KiB (0.00% increase, -0.31% of buffer)	768.463 → 768.472 → 771.220
✅	agent_deb_amd64_fips	+4.89 KiB (0.00% increase, -0.16% of buffer)	715.051 → 715.056 → 718.020
✅	agent_msi	+7.0 KiB (0.00% increase, -0.05% of buffer)	647.746 → 647.753 → 662.360
✅	agent_rpm_amd64	+8.89 KiB (0.00% increase, -0.32% of buffer)	768.447 → 768.456 → 771.190
✅	agent_rpm_amd64_fips	+4.89 KiB (0.00% increase, -0.16% of buffer)	715.035 → 715.040 → 718.020
✅	agent_rpm_arm64	+7.34 KiB (0.00% increase, -0.18% of buffer)	740.393 → 740.400 → 744.370
✅	agent_rpm_arm64_fips	+7.34 KiB (0.00% increase, -0.16% of buffer)	691.526 → 691.533 → 695.880
✅	agent_suse_amd64	+8.89 KiB (0.00% increase, -0.32% of buffer)	768.447 → 768.456 → 771.190
✅	agent_suse_amd64_fips	+4.89 KiB (0.00% increase, -0.16% of buffer)	715.035 → 715.040 → 718.020
✅	agent_suse_arm64	+7.34 KiB (0.00% increase, -0.18% of buffer)	740.393 → 740.400 → 744.370
✅	agent_suse_arm64_fips	+7.34 KiB (0.00% increase, -0.16% of buffer)	691.526 → 691.533 → 695.880
✅	docker_agent_amd64	+8.89 KiB (0.00% increase, -0.87% of buffer)	827.426 → 827.435 → 828.420
✅	docker_agent_arm64	+7.34 KiB (0.00% increase, -0.18% of buffer)	824.428 → 824.435 → 828.440
✅	docker_agent_jmx_amd64	+8.89 KiB (0.00% increase, -0.67% of buffer)	1018.339 → 1018.347 → 1019.630
✅	docker_agent_jmx_arm64	+7.34 KiB (0.00% increase, -0.18% of buffer)	1004.120 → 1004.127 → 1008.130

18 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_heroku_amd64	316.124 MiB
✅	docker_cluster_agent_amd64	212.687 MiB
✅	docker_cluster_agent_arm64	225.718 MiB
✅	docker_cws_instrumentation_amd64	7.439 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.557 MiB
✅	docker_dogstatsd_arm64	37.686 MiB
✅	docker_host_profiler_amd64	307.574 MiB
✅	docker_host_profiler_arm64	318.791 MiB
✅	dogstatsd_deb_amd64	30.303 MiB
✅	dogstatsd_deb_arm64	28.315 MiB
✅	dogstatsd_rpm_amd64	30.303 MiB
✅	dogstatsd_suse_amd64	30.303 MiB
✅	iot_agent_deb_amd64	46.651 MiB
✅	iot_agent_deb_arm64	43.280 MiB
✅	iot_agent_deb_armhf	44.097 MiB
✅	iot_agent_rpm_amd64	46.651 MiB
✅	iot_agent_suse_amd64	46.650 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 57c00082-f715-4fb6-b8d8-dedb977f789f

Baseline: 7d78172
Comparison: b1708b2
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	+0.77	[-0.09, +1.62]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	+0.70	[+0.58, +0.83]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	+0.23	[+0.18, +0.28]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	+0.18	[-0.04, +0.39]	1	Logs
➖	quality_gate_security_no_fs_load	memory utilization	-0.19	[-0.27, -0.12]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	-0.23	[-0.28, -0.18]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.24	[-0.47, -0.01]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.38	[-0.42, -0.34]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.41	[-0.45, -0.37]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	-0.41	[-0.65, -0.17]	1	Logs

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.76MiB ≤ 179MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	747.45KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	2 ≤ 5	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	473.83MiB ≤ 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	16 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	212.53MiB ≤ 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.52MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	362.80 ≤ 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	428.06MiB ≤ 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.72MiB ≤ 75MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	33.74 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	329.69MiB ≤ 355MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	62.81 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	311.27MiB ≤ 335MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	23.43 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	315.61MiB ≤ 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_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_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, 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_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 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 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_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_all_features, 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_private_action_runner, 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.