Skip to content

Update module github.com/DataDog/dd-trace-go/contrib/net/http/v2 to v2.2.3#50299

Open
renovate[bot] wants to merge 3 commits intomainfrom
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
Open

Update module github.com/DataDog/dd-trace-go/contrib/net/http/v2 to v2.2.3#50299
renovate[bot] wants to merge 3 commits intomainfrom
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 4, 2026

This PR contains the following updates:

Package Change Age Confidence
github.com/DataDog/dd-trace-go/contrib/net/http/v2 v2.0.1v2.2.3 age confidence

Warning

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


Release Notes

DataDog/dd-trace-go (github.com/DataDog/dd-trace-go/contrib/net/http/v2)

v2.2.3

Compare Source

What's Changed

This patch release fixes a significant bug that caused dropped spans due to local sampling rules overriding the sampling decision already present in inbound distributed trace context.

[!IMPORTANT]
Depending on your sampling rules, and especially if you have trace sampling rules,, you may notice an increase in ingested spans. This increase is expected and the consequence of not applying trace sampling rules when there is a head sampling decision. If the ingested volume is problematic, reduce it using APM Ingestion Controls. For any questions or issues, please contact Datadog Support.

Application Performance Monitoring (APM)

Full Changelog: DataDog/dd-trace-go@v2.2.2...v2.2.3

v2.2.2

Compare Source

[!NOTE]
v2.2.0 and v2.2.1 are retracted versions. If you are running one these two versions, please upgrade to v2.2.2 as soon as possible.

[!WARNING]
If you are experiencing sporadic spotaneous reboots by running dd-trace-go on Mac M4 15.5 or 15.6. Please upgrade to v2.2.2 as soon as possible. More information in #​3827

What's Changed

Application Performance Monitoring (APM)
App & API Protection
Profiling
Ci Visibility
General

New Contributors

Full Changelog: DataDog/dd-trace-go@v2.1.0...v2.2.0

v2.1.0

Compare Source

Summary

Application Performance Monitoring (APM)
Client-Side Stats Computation

Client-Side Stats computation is now enabled by default. This feature allows the Go tracer to compute aggregated span statistics locally before sending them to the Datadog Agent, resulting in reduced network traffic and improved performance.

What this means: Instead of sending all raw span data to the Agent, the tracer now sends pre-computed statistics, reducing bandwidth usage while maintaining full observability.

To disable, if needed: Set the environment variable DD_TRACE_STATS_COMPUTATION_ENABLED=false or use tracer.WithStatsComputation(false) when starting the tracer programmatically.

File-based Configurations

Introduced support for configuring SDK products via a file on the underlying Linux system. #​3438 Documentation

Baggage improvements

Fixed a distributed tracing bug in the baggage propagator. Also refactored baggage injection and extraction logic for improved performance and readability. #​3439 #​3597

Application Security Management (ASM)

contrib envoyproxy/go-control-plane:

  • API Security
    • Proxy sampler has been implemented for schema generation
    • Support of Json body analysis of requests and responses (using simdjson-go or fallbacking on json-iterator/go if not available)
  • Appsec
    • Support of Envoy observability_mode for async and non-blocking requests analysis

What's Changed

Application Performance Monitoring (APM)
Application Security Management (ASM)
Profiling
CI Visibility
General

New Contributors

Full Changelog: DataDog/dd-trace-go@v2.0.0...v2.1.0


Configuration

📅 Schedule: (UTC)

  • 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 renovate Bot added changelog/no-changelog No changelog entry needed dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency qa/no-code-change No code change in Agent code requiring validation labels May 4, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 4, 2026

ℹ️ 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):

  • 1 additional dependency was updated

Details:

Package Change
github.com/DataDog/dd-trace-go/v2 v2.2.3-rc.1 -> v2.2.3

@dd-prapprover
Copy link
Copy Markdown

dd-prapprover Bot commented May 4, 2026

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-05-07T08:44:15Z
  • ⬜ CI tests passed
  • ⬜ Approved
  • ⬜ Merge Started
  • ⬜ Merged

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

@dd-octo-sts dd-octo-sts Bot added the internal Identify a non-fork PR label May 4, 2026
@github-actions github-actions Bot added the short review PR is simple enough to be reviewed quickly label May 4, 2026
@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 4, 2026

Files inventory check summary

File checks results against ancestor a4176470:

Results for datadog-agent_7.80.0~devel.git.562.d07640f.pipeline.112038287-1_amd64.deb:

No change detected

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 4, 2026

Static quality checks

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

32 successful checks with minimal change (< 2 KiB)
Quality gate Current Size
agent_deb_amd64 742.347 MiB
agent_deb_amd64_fips 700.414 MiB
agent_heroku_amd64 309.210 MiB
agent_rpm_amd64 742.331 MiB
agent_rpm_amd64_fips 700.397 MiB
agent_rpm_arm64 720.235 MiB
agent_rpm_arm64_fips 681.397 MiB
agent_suse_amd64 742.331 MiB
agent_suse_amd64_fips 700.397 MiB
agent_suse_arm64 720.235 MiB
agent_suse_arm64_fips 681.397 MiB
docker_agent_amd64 802.578 MiB
docker_agent_arm64 805.334 MiB
docker_agent_jmx_amd64 993.497 MiB
docker_agent_jmx_arm64 985.033 MiB
docker_cluster_agent_amd64 206.626 MiB
docker_cluster_agent_arm64 220.634 MiB
docker_cws_instrumentation_amd64 7.142 MiB
docker_cws_instrumentation_arm64 6.689 MiB
docker_host_profiler_amd64 301.580 MiB
docker_host_profiler_arm64 313.117 MiB
docker_dogstatsd_amd64 39.507 MiB
docker_dogstatsd_arm64 37.690 MiB
dogstatsd_deb_amd64 30.161 MiB
dogstatsd_deb_arm64 28.290 MiB
dogstatsd_rpm_amd64 30.161 MiB
dogstatsd_suse_amd64 30.161 MiB
iot_agent_deb_amd64 44.486 MiB
iot_agent_deb_arm64 41.463 MiB
iot_agent_deb_armhf 42.203 MiB
iot_agent_rpm_amd64 44.487 MiB
iot_agent_suse_amd64 44.487 MiB

@cit-pr-commenter-54b7da
Copy link
Copy Markdown

cit-pr-commenter-54b7da Bot commented May 4, 2026

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a5b9c460-6f87-414c-a516-b131f12d3782

Baseline: a417647
Comparison: d07640f
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 -2.92 [-5.78, -0.06] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_logs % cpu utilization +2.74 [+1.76, +3.72] 1 Logs bounds checks dashboard
otlp_ingest_metrics memory utilization +0.42 [+0.26, +0.57] 1 Logs
ddot_metrics memory utilization +0.38 [+0.18, +0.58] 1 Logs
uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization +0.35 [+0.30, +0.41] 1 Logs
quality_gate_idle memory utilization +0.15 [+0.10, +0.20] 1 Logs bounds checks dashboard
file_to_blackhole_500ms_latency egress throughput +0.05 [-0.37, +0.47] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.02 [-0.18, +0.22] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.01 [-0.09, +0.11] 1 Logs
quality_gate_idle_all_features memory utilization +0.01 [-0.03, +0.05] 1 Logs bounds checks dashboard
file_to_blackhole_100ms_latency egress throughput +0.00 [-0.17, +0.18] 1 Logs
uds_dogstatsd_to_api_v3 ingress throughput -0.00 [-0.20, +0.20] 1 Logs
ddot_metrics_sum_delta memory utilization -0.03 [-0.22, +0.17] 1 Logs
file_to_blackhole_1000ms_latency egress throughput -0.05 [-0.51, +0.41] 1 Logs
file_to_blackhole_0ms_latency egress throughput -0.10 [-0.65, +0.45] 1 Logs
quality_gate_security_no_fs_load memory utilization -0.15 [-0.26, -0.04] 1 Logs bounds checks dashboard
quality_gate_security_mean_fs_load memory utilization -0.18 [-0.22, -0.14] 1 Logs bounds checks dashboard
ddot_metrics_sum_cumulativetodelta_exporter memory utilization -0.26 [-0.50, -0.02] 1 Logs
quality_gate_security_idle memory utilization -0.26 [-0.33, -0.18] 1 Logs bounds checks dashboard
docker_containers_memory memory utilization -0.32 [-0.42, -0.21] 1 Logs
ddot_logs memory utilization -0.40 [-0.48, -0.33] 1 Logs
ddot_metrics_sum_cumulative memory utilization -0.42 [-0.57, -0.26] 1 Logs
otlp_ingest_logs memory utilization -0.60 [-0.70, -0.50] 1 Logs
quality_gate_metrics_logs memory utilization -0.80 [-1.05, -0.55] 1 Logs bounds checks dashboard
tcp_syslog_to_blackhole ingress throughput -0.82 [-1.04, -0.60] 1 Logs
docker_containers_cpu % cpu utilization -2.92 [-5.78, -0.06] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed observed_value links
docker_containers_cpu simple_check_run 10/10 719 ≥ 26
docker_containers_memory memory_usage 10/10 244.05MiB ≤ 370MiB
docker_containers_memory simple_check_run 10/10 697 ≥ 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.21GiB ≤ 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 141.99MiB ≤ 147MiB 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 473.74MiB ≤ 495MiB bounds checks dashboard
quality_gate_logs intake_connections 10/10 4 ≤ 6 bounds checks dashboard
quality_gate_logs memory_usage 10/10 181.03MiB ≤ 195MiB bounds checks dashboard
quality_gate_logs missed_bytes 10/10 0B = 0B bounds checks dashboard
quality_gate_metrics_logs cpu_usage 10/10 361.94 ≤ 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 370.79MiB ≤ 430MiB bounds checks dashboard
quality_gate_metrics_logs missed_bytes 10/10 0B = 0B bounds checks dashboard
quality_gate_security_idle cpu_usage 10/10 24.70 ≤ 40 bounds checks dashboard
quality_gate_security_idle memory_usage 10/10 291.90MiB ≤ 330MiB bounds checks dashboard
quality_gate_security_mean_fs_load cpu_usage 10/10 54.51 ≤ 70 bounds checks dashboard
quality_gate_security_mean_fs_load memory_usage 10/10 267.75MiB ≤ 320MiB bounds checks dashboard
quality_gate_security_no_fs_load cpu_usage 10/10 21.73 ≤ 40 bounds checks dashboard
quality_gate_security_no_fs_load memory_usage 10/10 278.16MiB ≤ 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".

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_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_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_logs, bounds check missed_bytes: 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_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.
  • 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.

@renovate renovate Bot force-pushed the renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x branch from 3645730 to 85e2531 Compare May 7, 2026 08:44
@datadog-prod-us1-5

This comment has been minimized.

@chouetz chouetz requested a review from a team as a code owner May 7, 2026 12:28
@github-actions github-actions Bot added long review PR is complex, plan time to review it and removed short review PR is simple enough to be reviewed quickly labels May 7, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 7, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@ajwerner
Copy link
Copy Markdown
Contributor

ajwerner commented May 7, 2026

technically this is just a test program not code that is used, but if you give me a few I'll rebase it anyway

…2.3 update

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@chouetz
Copy link
Copy Markdown
Member

chouetz commented May 7, 2026

technically this is just a test program not code that is used, but if you give me a few I'll rebase it anyway

@ajwerner I was not really sure of what I was doing, I generated this as well as a follow-up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/no-changelog No changelog entry needed dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency internal Identify a non-fork PR long review PR is complex, plan time to review it qa/no-code-change No code change in Agent code requiring validation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants