[Backport 7.78.x] Extend agent builder script to include integrations without manifest.json

[sarah-witt]

Backport 0f8f268 from #49547.

What does this PR do?

We started to migrate away from manifest.json. New integrations are created without one. This change aims to change the logic to look at config.toml of the integrations-core repo to see ship some of these new integrations.

https://github.com/DataDog/integrations-core/blob/master/.ddev/config.toml#L244

Integrations that are missing:

• control_m
• krakend
• lustre
• n8n
• prefect

Force cached rebuild here to test (not sure if that needs to happen in this PR): #49553

I checked the artifact for arm build in the CI triggered by the above and the check are there. https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/1607210425

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

[agent-platform-auto-pr]

Files inventory check summary

File checks results against ancestor ce1832e5:

Results for datadog-agent_7.78.0.git.14.3a044ef.pipeline.108498323-1_amd64.deb:

No change detected

[agent-platform-auto-pr]

Static quality checks

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

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	docker_agent_amd64	-5.34 KiB (0.00% reduction)	807.976 → 807.970 → 815.700
✅	docker_agent_arm64	-5.32 KiB (0.00% reduction)	811.125 → 811.119 → 821.970
✅	docker_agent_jmx_amd64	-5.34 KiB (0.00% reduction)	998.891 → 998.886 → 1006.580
✅	docker_agent_jmx_arm64	-5.31 KiB (0.00% reduction)	990.819 → 990.813 → 1001.570

27 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	747.682 MiB
✅	agent_deb_amd64_fips	704.558 MiB
✅	agent_heroku_amd64	309.529 MiB
✅	agent_msi	599.770 MiB
✅	agent_rpm_amd64	747.665 MiB
✅	agent_rpm_amd64_fips	704.542 MiB
✅	agent_rpm_arm64	726.044 MiB
✅	agent_rpm_arm64_fips	685.958 MiB
✅	agent_suse_amd64	747.665 MiB
✅	agent_suse_amd64_fips	704.542 MiB
✅	agent_suse_arm64	726.044 MiB
✅	agent_suse_arm64_fips	685.958 MiB
✅	docker_cluster_agent_amd64	205.404 MiB
✅	docker_cluster_agent_arm64	219.742 MiB
✅	docker_cws_instrumentation_amd64	7.142 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	39.222 MiB
✅	docker_dogstatsd_arm64	37.436 MiB
✅	dogstatsd_deb_amd64	29.874 MiB
✅	dogstatsd_deb_arm64	28.027 MiB
✅	dogstatsd_rpm_amd64	29.874 MiB
✅	dogstatsd_suse_amd64	29.874 MiB
✅	iot_agent_deb_amd64	43.257 MiB
✅	iot_agent_deb_arm64	40.308 MiB
✅	iot_agent_deb_armhf	41.052 MiB
✅	iot_agent_rpm_amd64	43.258 MiB
✅	iot_agent_suse_amd64	43.258 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-7.77 KiB (0.00% reduction)	174.028 → 174.021 → 178.360
✅	agent_deb_amd64_fips	-12.73 KiB (0.01% reduction)	164.797 → 164.784 → 172.790
✅	agent_heroku_amd64	-2.79 KiB (0.00% reduction)	74.452 → 74.449 → 79.970
✅	agent_msi	-16.0 KiB (0.01% reduction)	137.672 → 137.656 → 146.220
✅	agent_rpm_amd64	-10.43 KiB (0.01% reduction)	176.864 → 176.853 → 181.830
✅	agent_rpm_amd64_fips	-20.1 KiB (0.01% reduction)	166.733 → 166.714 → 173.370
✅	agent_rpm_arm64	+23.46 KiB (0.01% increase)	158.866 → 158.889 → 163.060
✅	agent_rpm_arm64_fips	+14.34 KiB (0.01% increase)	150.734 → 150.748 → 156.170
✅	agent_suse_amd64	-10.43 KiB (0.01% reduction)	176.864 → 176.853 → 181.830
✅	agent_suse_amd64_fips	-20.1 KiB (0.01% reduction)	166.733 → 166.714 → 173.370
✅	agent_suse_arm64	+23.46 KiB (0.01% increase)	158.866 → 158.889 → 163.060
✅	agent_suse_arm64_fips	+14.34 KiB (0.01% increase)	150.734 → 150.748 → 156.170
✅	docker_agent_amd64	+3.49 KiB (0.00% increase)	267.243 → 267.246 → 272.480
✅	docker_agent_arm64	-2.7 KiB (0.00% reduction)	254.441 → 254.438 → 261.060
✅	docker_agent_jmx_amd64	-3.27 KiB (0.00% reduction)	335.896 → 335.892 → 341.100
✅	docker_agent_jmx_arm64	-2.68 KiB (0.00% reduction)	319.075 → 319.072 → 325.620
✅	docker_cluster_agent_amd64	-4.12 KiB (0.01% reduction)	71.970 → 71.965 → 72.920
✅	docker_cluster_agent_arm64	-6.34 KiB (0.01% reduction)	67.541 → 67.535 → 68.220
✅	docker_cws_instrumentation_amd64	neutral	2.999 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.729 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	15.162 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.477 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.891 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.775 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.901 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.901 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.396 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.699 MiB → 10.450
✅	iot_agent_deb_armhf	neutral	9.936 MiB → 10.620
✅	iot_agent_rpm_amd64	neutral	11.412 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.412 MiB → 12.060

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 0335d8dd-f174-4802-a15a-7ee06fd64680

Baseline: ce1832e
Comparison: 3a044ef
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	+1.99	[-1.07, +5.05]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+1.99	[-1.07, +5.05]	1	Logs
➖	quality_gate_logs	% cpu utilization	+1.28	[-0.26, +2.82]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	+0.88	[+0.65, +1.11]	1	Logs bounds checks dashboard
➖	otlp_ingest_metrics	memory utilization	+0.52	[+0.36, +0.67]	1	Logs
➖	ddot_metrics	memory utilization	+0.44	[+0.26, +0.61]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.18	[+0.15, +0.22]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	+0.09	[-0.01, +0.18]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.03	[-0.41, +0.47]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.02	[-0.44, +0.48]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.02	[-0.18, +0.22]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.20, +0.21]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.11, +0.11]	1	Logs
➖	quality_gate_idle	memory utilization	-0.02	[-0.07, +0.03]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_delta	memory utilization	-0.03	[-0.20, +0.14]	1	Logs
➖	file_tree	memory utilization	-0.05	[-0.11, +0.01]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.07	[-0.20, +0.06]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.09	[-0.47, +0.30]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.09	[-0.16, -0.02]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.35	[-0.57, -0.12]	1	Logs
➖	docker_containers_memory	memory utilization	-0.46	[-0.54, -0.39]	1	Logs
➖	ddot_logs	memory utilization	-0.47	[-0.54, -0.40]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.52	[-0.58, -0.46]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.78	[-0.92, -0.64]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	610 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	272.55MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	725 ≥ 26
✅	file_to_blackhole_0ms_latency	memory_usage	10/10	0.19GiB ≤ 1.20GiB
✅	file_to_blackhole_0ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10	0.23GiB ≤ 1.20GiB
✅	file_to_blackhole_1000ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_100ms_latency	memory_usage	10/10	0.20GiB ≤ 1.20GiB
✅	file_to_blackhole_100ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_500ms_latency	memory_usage	10/10	0.21GiB ≤ 1.20GiB
✅	file_to_blackhole_500ms_latency	missed_bytes	10/10	0B = 0B
✅	quality_gate_idle	intake_connections	10/10	3 = 3	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	174.25MiB ≤ 175MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	2 ≤ 3	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	490.82MiB ≤ 550MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	204.58MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	340.15 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	405.97MiB ≤ 475MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	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_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_metrics_logs, bounds check intake_connections: 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.
• quality_gate_metrics_logs, bounds check cpu_usage: 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_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 missed_bytes: 10/10 replicas passed. Gate passed.

[AliDatadog]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-04-20 12:52:04 UTC ℹ️ Start processing command /merge

---

2026-04-20 12:52:08 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in 7.78.x is approximately 1h (p90).

---

2026-04-20 14:42:05 UTC ℹ️ MergeQueue: This merge request was merged