[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker.io/ubuntu (source)	final	major	24.04 → 26.04
docker.io/ubuntu (source)	stage	major	24.04 → 26.04

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dd-prapprover]

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

• ✅ PR is eligible for auto-approval by rule datadog-agent-renovate - 2026-10-26T21:06:48Z
• ⬜ CI tests passed
• ⬜ Approved
• Manual merge required: this rule does not auto-merge.

➡️ Current phase: CI tests failed. Please fix the failing tests and rerun the workflow, click Workflow Link -> Workflow Starter Link -> Start Workflow

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.21% (-1.41%)

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

[dd-octo-sts]

Static quality checks

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

Error

	Quality gate	Change	Size (prev → curr → max)
❌	docker_agent_amd64 (on disk)	+23.34 MiB (2.89% increase, -9719.46% of buffer)	806.600 → 829.944 → 806.840
❌	docker_agent_arm64 (on disk)	+20.83 MiB (2.58% increase, -1856.83% of buffer)	808.998 → 829.830 → 810.120
❌	docker_agent_jmx_amd64 (on disk)	+24.35 MiB (2.44% increase, -40934.42% of buffer)	997.541 → 1021.892 → 997.600
❌	docker_agent_jmx_arm64 (on disk)	+21.76 MiB (2.20% increase, -1800.39% of buffer)	988.591 → 1010.354 → 989.800
❌	docker_cluster_agent_amd64 (on disk)	+28.54 MiB (13.77% increase, -6126.37% of buffer)	207.244 → 235.780 → 207.710
❌	docker_cluster_agent_arm64 (on disk)	+26.27 MiB (11.88% increase, -580389.70% of buffer)	221.205 → 247.480 → 221.210
❌	docker_host_profiler_amd64 (on disk)	+16.99 MiB (5.62% increase, -123.59% of buffer)	302.136 → 319.123 → 315.880
❌	docker_host_profiler_arm64 (per-PR wire threshold)	+5.81 MiB (5.52% increase, -39.37% of buffer)	N/A

Gate failure full details

Quality gate	Error type	Error message
docker_agent_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_amd64 failed! Disk size 829.9 MB exceeds limit of 806.8 MB by 23.1 MB
docker_agent_arm64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_arm64 failed! Disk size 829.8 MB exceeds limit of 810.1 MB by 19.7 MB
docker_agent_jmx_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_jmx_amd64 failed! Disk size 1021.9 MB exceeds limit of 997.6 MB by 24.3 MB
docker_agent_jmx_arm64	AbsoluteLimitExceeded	static_quality_gate_docker_agent_jmx_arm64 failed! Disk size 1010.4 MB exceeds limit of 989.8 MB by 20.6 MB
docker_cluster_agent_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_cluster_agent_amd64 failed! Disk size 235.8 MB exceeds limit of 207.7 MB by 28.1 MB
docker_cluster_agent_arm64	AbsoluteLimitExceeded	static_quality_gate_docker_cluster_agent_arm64 failed! Disk size 247.5 MB exceeds limit of 221.2 MB by 26.3 MB
docker_host_profiler_amd64	AbsoluteLimitExceeded	static_quality_gate_docker_host_profiler_amd64 failed! Disk size 319.1 MB exceeds limit of 315.9 MB by 3.2 MB
docker_host_profiler_arm64	PerPRWireThresholdExceeded	On-wire size increase of 5.81 MiB exceeds the per-PR wire threshold of 5.0 MiB

Static quality gates prevent the PR to merge!
You can check the static quality gates confluence page for guidance. We also have a toolbox page available to list tools useful to debug the size increase.
Please either fix the size violation or request an exception.

24 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	746.465 MiB
✅	agent_deb_amd64_fips	704.112 MiB
✅	agent_heroku_amd64	310.785 MiB
✅	agent_rpm_amd64	746.449 MiB
✅	agent_rpm_amd64_fips	704.096 MiB
✅	agent_rpm_arm64	724.018 MiB
✅	agent_rpm_arm64_fips	684.780 MiB
✅	agent_suse_amd64	746.449 MiB
✅	agent_suse_amd64_fips	704.096 MiB
✅	agent_suse_arm64	724.018 MiB
✅	agent_suse_arm64_fips	684.780 MiB
✅	docker_cws_instrumentation_amd64	7.154 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	39.519 MiB
✅	docker_dogstatsd_arm64	37.690 MiB
✅	dogstatsd_deb_amd64	30.174 MiB
✅	dogstatsd_deb_arm64	28.296 MiB
✅	dogstatsd_rpm_amd64	30.174 MiB
✅	dogstatsd_suse_amd64	30.174 MiB
✅	iot_agent_deb_amd64	44.472 MiB
✅	iot_agent_deb_arm64	41.437 MiB
✅	iot_agent_deb_armhf	42.154 MiB
✅	iot_agent_rpm_amd64	44.473 MiB
✅	iot_agent_suse_amd64	44.472 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 7577e0cd-dc03-4afa-b4e6-7d0e8c14e7c5

Baseline: 3a78e58
Comparison: 3554c6194e10c29894af8a738535c505d2676dc7
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.10	[-4.03, +1.83]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_metrics_logs	memory utilization	+0.77	[+0.52, +1.02]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.31	[+0.07, +0.55]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.26	[+0.21, +0.31]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.24	[+0.09, +0.39]	1	Logs
➖	file_tree	memory utilization	+0.19	[+0.15, +0.23]	1	Logs
➖	quality_gate_idle	memory utilization	+0.14	[+0.09, +0.18]	1	Logs bounds checks dashboard
➖	docker_containers_memory	memory utilization	+0.07	[-0.03, +0.17]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	+0.05	[-0.18, +0.28]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.04	[-0.10, +0.18]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.03	[-0.41, +0.47]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.21, +0.21]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.00	[-0.20, +0.20]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.01	[-0.10, +0.09]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.01	[-0.17, +0.15]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.04	[-0.43, +0.36]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.12	[-0.62, +0.39]	1	Logs
➖	ddot_metrics	memory utilization	-0.19	[-0.38, +0.01]	1	Logs
➖	ddot_logs	memory utilization	-0.22	[-0.29, -0.16]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.26	[-0.45, -0.07]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.33	[-0.43, -0.24]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.35	[-0.39, -0.31]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-0.48	[-1.51, +0.56]	1	Logs bounds checks dashboard
➖	docker_containers_cpu	% cpu utilization	-1.10	[-4.03, +1.83]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	603 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	247.96MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	709 ≥ 26
✅	file_to_blackhole_0ms_latency	memory_usage	10/10	0.16GiB ≤ 1.20GiB
✅	file_to_blackhole_0ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10	0.20GiB ≤ 1.20GiB
✅	file_to_blackhole_1000ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_100ms_latency	memory_usage	10/10	0.17GiB ≤ 1.20GiB
✅	file_to_blackhole_100ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_500ms_latency	memory_usage	10/10	0.18GiB ≤ 1.20GiB
✅	file_to_blackhole_500ms_latency	missed_bytes	10/10	0B = 0B
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	143.85MiB ≤ 147MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	740.96KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	471.25MiB ≤ 495MiB	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	3 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	178.09MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.34MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	344.31 ≤ 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	382.87MiB ≤ 430MiB	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.93GiB ≤ 1.04GiB	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_idle_all_features, bounds check total_bytes_received: 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 total_bytes_received: 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 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 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 missed_bytes: 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 intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[dd-prapprover]

This PR has been automatically approved by the DD PR Approver bot.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-03 21:55:11 UTC ℹ️ Start processing command /merge

---

2026-06-03 21:55:18 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-06-04 02:44:13 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

new commit added, dismiss all previous approvals

[aiuto]

All the docker tests fail. This needs manual intervention if we want it.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 26.x releases. But if you manually upgrade to 26.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[dd-prapprover]

This PR has been automatically approved by the DD PR Approver bot.

[dd-octo-sts]

This pull request has been automatically marked as stale because it has not had activity in the past 15 days.

It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window.

Thank you for your contributions!

[dd-octo-sts]

This pull request has been automatically marked as stale because it has not had activity in the past 15 days.

It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window.

Thank you for your contributions!

[dd-octo-sts]

This pull request has been automatically marked as stale because it has not had activity in the past 15 days.

It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window.

Thank you for your contributions!

new commit added, dismiss all previous approvals