Update module gopkg.in/DataDog/dd-trace-go.v1 to v1.74.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
gopkg.in/DataDog/dd-trace-go.v1	v1.73.1 → v1.74.8

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

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 this update again.

---

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

---

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

[renovate]

ℹ️ Artifact update notice

File name: pkg/dyninst/testprogs/progs/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 6 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.23.1 -> 1.24.0
github.com/DataDog/dd-trace-go/contrib/net/http/v2	v2.2.3 -> v2.3.0
github.com/DataDog/dd-trace-go/v2	v2.2.3 -> v2.3.0
github.com/go-viper/mapstructure/v2	v2.3.0 -> v2.4.0
github.com/hashicorp/go-secure-stdlib/parseutil	v0.1.7 -> v0.2.0
github.com/hashicorp/go-sockaddr	v1.0.2 -> v1.0.7
golang.org/x/exp	v0.0.0-20250408133849-7e4ce0ab07d0 -> v0.0.0-20250606033433-dcc06ee1d476

[dd-prapprover-prod-77c48c]

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-07-03T10:39:20Z
• ⬜ CI tests passed
• ⬜ Approved
• Manual merge required: this rule does not auto-merge.

➡️ Current phase: CI tests failed. Please fix the failing tests to continue.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0c64378bda

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep testprog module compatible with Go 1.23 builds

This module is still regenerated by dda inv system-probe.build-dyninst-test-programs for go1.23.11 and the generated Ninja rule pins GOTOOLCHAIN to that version (tasks/system_probe.py:1883 and tasks/system_probe.py:1936). Raising the module directive to go 1.24.0 makes every Go 1.23.x invocation fail before listing or building packages with go.mod requires go >= 1.24.0, so the dyninst Go 1.23 test binaries can no longer be regenerated unless the module stays 1.23-compatible or the Go 1.23 target is removed/updated.

Useful? React with 👍 / 👎.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 6c9376ee:

Results for datadog-agent_7.82.0~devel.git.425.0c64378.pipeline.122555807-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 bcc2287
📊 Static Quality Gates Dashboard
🔗 SQG Job
SOME SIZE DELTAS ARE N/A (ANCESTOR METRICS NOT YET AVAILABLE). RETRY JOB

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	N/A	N/A → 748.605 → 758.200
✅	agent_deb_amd64_fips	N/A	N/A → 703.637 → 709.840
✅	agent_heroku_amd64	N/A	N/A → 307.845 → 315.230
✅	agent_rpm_amd64	N/A	N/A → 748.589 → 758.170
✅	agent_rpm_amd64_fips	N/A	N/A → 703.621 → 709.840
✅	agent_rpm_arm64	N/A	N/A → 723.888 → 729.660
✅	agent_rpm_arm64_fips	N/A	N/A → 682.671 → 688.860
✅	agent_suse_amd64	N/A	N/A → 748.589 → 758.170
✅	agent_suse_amd64_fips	N/A	N/A → 703.621 → 709.840
✅	agent_suse_arm64	N/A	N/A → 723.888 → 729.660
✅	agent_suse_arm64_fips	N/A	N/A → 682.671 → 688.860
✅	docker_agent_amd64	N/A	N/A → 807.406 → 813.790
✅	docker_agent_arm64	N/A	N/A → 807.748 → 815.030
✅	docker_agent_jmx_amd64	N/A	N/A → 998.303 → 1004.550
✅	docker_agent_jmx_arm64	N/A	N/A → 987.298 → 994.710
✅	docker_cluster_agent_amd64	N/A	N/A → 209.267 → 210.470
✅	docker_cluster_agent_arm64	N/A	N/A → 222.388 → 222.980
✅	docker_cws_instrumentation_amd64	N/A	N/A → 7.447 → 7.480
✅	docker_cws_instrumentation_arm64	N/A	N/A → 6.877 → 7.110
✅	docker_dogstatsd_amd64	N/A	N/A → 39.125 → 39.910
✅	docker_dogstatsd_arm64	N/A	N/A → 37.242 → 38.270
✅	docker_host_profiler_amd64	N/A	N/A → 305.406 → 317.640
✅	docker_host_profiler_arm64	N/A	N/A → 316.500 → 328.900
✅	dogstatsd_deb_amd64	N/A	N/A → 29.864 → 31.150
✅	dogstatsd_deb_arm64	N/A	N/A → 27.908 → 29.530
✅	dogstatsd_rpm_amd64	N/A	N/A → 29.864 → 31.150
✅	dogstatsd_suse_amd64	N/A	N/A → 29.864 → 31.150
✅	iot_agent_deb_amd64	N/A	N/A → 45.766 → 46.380
✅	iot_agent_deb_arm64	N/A	N/A → 42.473 → 43.720
✅	iot_agent_deb_armhf	N/A	N/A → 43.258 → 43.960
✅	iot_agent_rpm_amd64	N/A	N/A → 45.767 → 46.380
✅	iot_agent_suse_amd64	N/A	N/A → 45.766 → 46.380

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 52b8bccc-f6a7-446e-9039-dd50002c526a

Baseline: fe5058b
Comparison: 989ace4
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.86	[-0.24, +1.96]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.37	[+0.33, +0.42]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.29	[+0.25, +0.33]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	+0.23	[+0.12, +0.34]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.01	[-0.05, +0.03]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.11	[-0.36, +0.14]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.16	[-0.22, -0.09]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	145.78MiB ≤ 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	579.56KiB ≤ 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	489.01MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	0.89MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	182.07MiB ≤ 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.20MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	331.95 ≤ 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	397.74MiB ≤ 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.86GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	29.23 ≤ 40	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	300.22MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	60.40 ≤ 80	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	274.91MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	23.38 ≤ 40	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	283.88MiB ≤ 320MiB	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
quality_gate_idle_all_features	baseline	10	Oom killed	Debug Dashboard
quality_gate_idle_all_features	comparison	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	comparison	10	Oom killed	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_metrics_logs, bounds check total_bytes_received: 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 cpu_usage: 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_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_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 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_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_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_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_logs, 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_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.74.8). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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