Skip to content

Update module github.com/DataDog/dd-trace-go/v2 to v2.8.2#52521

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-datadog-dd-trace-go-v2-2.x
Open

Update module github.com/DataDog/dd-trace-go/v2 to v2.8.2#52521
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-datadog-dd-trace-go-v2-2.x

Conversation

@renovate

@renovate renovate Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/DataDog/dd-trace-go/v2 v2.2.3v2.8.2 age adoption passing 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/v2)

v2.8.2

Compare Source

What's Changed

General
  • fix(ddtrace/tracer): wire version on aggregation key when adding a span to client-side stats by @​darccio in #​4734

Full Changelog: DataDog/dd-trace-go@v2.8.1...v2.8.2

v2.8.1

Compare Source

Application Performance Monitoring (APM)

Full Changelog: DataDog/dd-trace-go@v2.8.0...v2.8.1

v2.8.0

Compare Source

Summary

New integrations. Two new integrations land in this release: Azure API Management (APIM) callout processor for security (#​4620), and twmb/franz-go for Kafka (#​4250).

Data Streams Monitoring. All three major Kafka integrations — confluent-kafka-go (#​4470), segmentio/kafka-go (#​4477), and Sarama (#​4560) — now attach kafka_cluster_id for cluster-level visibility. TrackDataStreamsTransaction also gains span tagging and custom timestamp support (#​4499).

OpenTelemetry (OTel) and OTLP. The tracer can now export traces directly via the OpenTelemetry Protocol (OTLP), bypassing the Datadog Agent entirely (#​4600, #​4583). OTel process context v2 (OTLP proto format) is supported (#​4478), and the parentbased_always_on sampler works in OTLP mode (#​4567).

Large Language Model (LLM) Observability. Prompt tracking is now available for LLMObs spans (#​4608). Experiment scope propagates from APM baggage into spans automatically (#​4651).

Profiler. An experimental goroutine leak profile is available as opt-in (#​4420). The goroutine wait profile type has been removed — this is a breaking change for anyone using it explicitly (#​4589).

HTTP and tracing. A new environment variable DD_TRACE_HTTP_URL_QUERY_STRING_ALLOWLIST lets you whitelist query string parameters to keep unredacted (#​4562). A new tracer.StartSpanFromPropagatedContext API simplifies span creation from propagated contexts (#​4492). AWS EventBridge max payload size is bumped to 1 MB (#​4458). Envoy Service Extensions integration gains Unix Domain Socket (UDS) support (#​4463).

OpenFeature. Flag evaluation metrics now emit via OTel Metrics (#​4489), with allocation key tagging (#​4515) and Remote Configuration (RC) integration via FFE_FLAGS subscription at tracer startup (#​4495).

Bug fixes. gorm now respects DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED (#​4618). Redis and Valkey pipeline commands are joined with newlines, fixing agent obfuscation (#​4593). A race condition in HTTP client trace timings is resolved (#​4591). AppSec block responses now include a correct Content-Length header (#​4496), and spurious Remote Configuration errors are silenced when RC is disabled (#​4612). ContextWithSpan no longer panics on nil context (#​4313). The OTel bridge preserves keep/drop sampling decisions for unsampled spans (#​4631). User-provided DogStatsD addresses now correctly take priority over defaults (#​4575).

Performance. Trace ID hex encoding is cached (#​4481), the span metadata map is preallocated (#​4541), and locking is removed from both sampling priority access (#​4546) and the internal logger (#​4547) — reducing allocations and contention on hot paths.

CI Visibility. Bazel offline cache and payload-file modes are supported (#​4503). Known test pagination is implemented for large test suites (#​4509).

What's Changed

Application Performance Monitoring (APM)
Application Security Management (ASM)
  • fix(appsec): explicitly set Content-Length header in block request handler by @​RomainMuller in #​4496
  • fix(appsec): silence spurious errors when DD_REMOTE_CONFIGURATION_ENABLED=false by @​darccio in #​4612
CI Visibility
Data Streams Monitoring
Feature flags
LLM Observability
Profiling
General

New Contributors

Full Changelog: DataDog/dd-trace-go@v2.7.0...v2.8.0

v2.7.4

Compare Source

What's Changed

General

Full Changelog: DataDog/dd-trace-go@v2.7.3...v2.7.4

v2.7.3

Compare Source

Application Performance Monitoring (APM)
  • feat(contrib/valkey-io): bump valkey-go and add SetOnInvalidations wrapper by @​Scorfly in #​4657
  • feat(contrib/redis/rueidis): add SetOnInvalidations to dedicatedClient by @​darccio in #​4659

Full Changelog: DataDog/dd-trace-go@v2.7.2...v2.7.3

v2.7.2

Compare Source

What's Changed

Application Performance Monitoring (APM)
  • fix(tracer): preserve keep/drop possibility for OTel bridge on unsampled spans
    by @​genesor in #​4631 (cherry-picked in ed4ba63)

Full Changelog: DataDog/dd-trace-go@v2.7.1...v2.7.2

v2.7.1

Compare Source

What's Changed

Full Changelog: DataDog/dd-trace-go@v2.7.0...v2.7.1

v2.7.0

Compare Source

[!WARNING]
As per our version release policy, we are dropping support for Go 1.24 after the release of Go 1.26. Our minimum supported Go release is now Go 1.25.

[!NOTE]
v2.7.0 introduces a new method of tracking errors. In most cases, this should not break existing error traces if you are using Error Tracking. If you have problems, please feel free to open an issue!

What's Changed
Application Performance Monitoring (APM)
General

Note

PR body was truncated to here.


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 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 Jun 20, 2026
@renovate

renovate Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor Author

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

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

Details:

Package Change
go 1.23.1 -> 1.25.0
github.com/DataDog/datadog-agent/comp/core/tagger/origindetection v0.67.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/obfuscate v0.67.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/proto v0.67.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/remoteconfig/state v0.69.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/trace v0.67.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/util/log v0.67.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/util/scrubber v0.67.0 -> v0.77.0
github.com/DataDog/datadog-agent/pkg/version v0.67.0 -> v0.77.0
github.com/DataDog/datadog-go/v5 v5.6.0 -> v5.8.3
github.com/DataDog/go-libddwaf/v4 v4.3.2 -> v4.9.0
github.com/DataDog/go-runtime-metrics-internal v0.0.4-0.20250721125240-fdf1ef85b633 -> v0.0.4-0.20260217080614-b0f4edc38a6d
github.com/DataDog/go-sqllexer v0.1.6 -> v0.1.13
github.com/DataDog/sketches-go v1.4.7 -> v1.4.8
github.com/ebitengine/purego v0.8.4 -> v0.10.0
github.com/go-viper/mapstructure/v2 v2.3.0 -> v2.5.0
github.com/hashicorp/go-version v1.7.0 -> v1.8.0
github.com/lufia/plan9stats v0.0.0-20250317134145-8bc96cf8fc35 -> v0.0.0-20260216142805-b3301c5f2a88
github.com/philhofer/fwd v1.1.3-0.20240916144458-20a13a1f6b7c -> v1.2.0
github.com/secure-systems-lab/go-securesystemslib v0.9.0 -> v0.10.0
github.com/shirou/gopsutil/v4 v4.25.5 -> v4.26.2
github.com/tinylib/msgp v1.2.5 -> v1.6.3
github.com/tklauser/go-sysconf v0.3.15 -> v0.3.16
github.com/tklauser/numcpus v0.10.0 -> v0.11.0
go.opentelemetry.io/auto/sdk v1.1.0 -> v1.2.1
go.opentelemetry.io/collector/component v1.31.0 -> v1.51.1-0.20260205185216-81bc641f26c0
go.opentelemetry.io/collector/featuregate v1.31.0 -> v1.51.1-0.20260205185216-81bc641f26c0
go.opentelemetry.io/collector/pdata v1.31.0 -> v1.51.1-0.20260205185216-81bc641f26c0
go.opentelemetry.io/collector/pdata/pprofile v0.125.0 -> v0.145.1-0.20260205185216-81bc641f26c0
go.opentelemetry.io/otel v1.36.0 -> v1.41.0
go.opentelemetry.io/otel/log v0.11.0 -> v0.15.0
go.opentelemetry.io/otel/metric v1.36.0 -> v1.41.0
go.opentelemetry.io/otel/sdk v1.36.0 -> v1.40.0
go.opentelemetry.io/otel/trace v1.36.0 -> v1.41.0
go.uber.org/zap v1.27.0 -> v1.27.1
golang.org/x/exp v0.0.0-20250408133849-7e4ce0ab07d0 -> v0.0.0-20260209203927-2842357ff358
golang.org/x/mod v0.25.0 -> v0.33.0
golang.org/x/net v0.41.0 -> v0.51.0
golang.org/x/sys v0.35.0 -> v0.42.0
golang.org/x/text v0.26.0 -> v0.35.0
golang.org/x/time v0.12.0 -> v0.15.0
google.golang.org/genproto/googleapis/rpc v0.0.0-20250603155806-513f23925822 -> v0.0.0-20260209200024-4cfbd4190f57
google.golang.org/grpc v1.73.0 -> v1.79.3
gopkg.in/ini.v1 v1.67.0 -> v1.67.1

@renovate renovate Bot added dependencies-go PRs that bump a go dependency qa/no-code-change No code change in Agent code requiring validation labels Jun 20, 2026
@dd-prapprover

dd-prapprover Bot commented Jun 20, 2026

Copy link
Copy Markdown

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-06-20T13:31:04Z
  • ⬜ 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.

@dd-octo-sts dd-octo-sts Bot added the internal Identify a non-fork PR label Jun 20, 2026
@github-actions github-actions Bot added the medium review PR review might take time label Jun 20, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e60d898e45

ℹ️ 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".

// Version 2.2.3 is the first one that supports subscribing to the remote
// config product for SymDB upload requests.
github.com/DataDog/dd-trace-go/v2 v2.2.3
github.com/DataDog/dd-trace-go/v2 v2.8.2

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Do not require Go 1.25 for older testprog builds

This dd-trace-go version raises the testprogs module to go 1.25.0, but build_dyninst_test_programs still explicitly builds the same module with go1.23.11 and go1.24.3 (tasks/system_probe.py:1883) while forcing each exact toolchain via GOTOOLCHAIN={go_version} (tasks/system_probe.py:1936). Go's toolchain rules make the go line the minimum required version and exact GOTOOLCHAIN=go1.24.3 does not auto-upgrade, so dda inv system-probe.build-dyninst-test-programs cannot produce the configured Go 1.23/1.24 binary variants after this update; either keep a tracer version compatible with the oldest configured toolchain or drop/update those variants together.

Useful? React with 👍 / 👎.

@datadog-prod-us1-6

datadog-prod-us1-6 Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 4 Pipeline jobs failed

DataDog/datadog-agent | prepare_sysprobe_ebpf_functional_tests_arm64   View in Datadog   GitLab

DataDog/datadog-agent | prepare_sysprobe_ebpf_functional_tests_x64   View in Datadog   GitLab

DataDog/datadog-agent | tests_ebpf_arm64   View in Datadog   GitLab

View all 4 failed jobs.

ℹ️ Info

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 51.05% (+0.13%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e60d898 | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Files inventory check summary

File checks results against ancestor 6c4365f0:

Results for datadog-agent_7.82.0~devel.git.197.e60d898.pipeline.120041181-1_amd64.deb:

No change detected

@dd-octo-sts

dd-octo-sts Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Static quality checks

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

32 successful checks with minimal change (< 2 KiB)
Quality gate Current Size
agent_deb_amd64 749.078 MiB
agent_deb_amd64_fips 705.023 MiB
agent_heroku_amd64 309.985 MiB
agent_rpm_amd64 749.062 MiB
agent_rpm_amd64_fips 705.006 MiB
agent_rpm_arm64 724.679 MiB
agent_rpm_arm64_fips 684.236 MiB
agent_suse_amd64 749.062 MiB
agent_suse_amd64_fips 705.006 MiB
agent_suse_arm64 724.679 MiB
agent_suse_arm64_fips 684.236 MiB
docker_agent_amd64 808.817 MiB
docker_agent_arm64 809.415 MiB
docker_agent_jmx_amd64 999.714 MiB
docker_agent_jmx_arm64 988.964 MiB
docker_cluster_agent_amd64 207.989 MiB
docker_cluster_agent_arm64 221.188 MiB
docker_cws_instrumentation_amd64 7.447 MiB
docker_cws_instrumentation_arm64 6.877 MiB
docker_dogstatsd_amd64 39.082 MiB
docker_dogstatsd_arm64 37.257 MiB
docker_host_profiler_amd64 304.564 MiB
docker_host_profiler_arm64 315.680 MiB
dogstatsd_deb_amd64 29.741 MiB
dogstatsd_deb_arm64 27.800 MiB
dogstatsd_rpm_amd64 29.741 MiB
dogstatsd_suse_amd64 29.741 MiB
iot_agent_deb_amd64 45.566 MiB
iot_agent_deb_arm64 42.292 MiB
iot_agent_deb_armhf 43.077 MiB
iot_agent_rpm_amd64 45.566 MiB
iot_agent_suse_amd64 45.565 MiB

@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: d9931a0c-30c6-44a8-b9db-30dfb2e5e4fc

Baseline: 6c4365f
Comparison: e60d898
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 +2.14 [+1.07, +3.21] 1 Logs bounds checks dashboard
quality_gate_metrics_logs memory utilization +0.88 [+0.63, +1.13] 1 Logs bounds checks dashboard
quality_gate_idle_all_features memory utilization -0.10 [-0.14, -0.06] 1 Logs bounds checks dashboard
quality_gate_idle memory utilization -0.49 [-0.54, -0.44] 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 144.68MiB ≤ 154MiB bounds checks dashboard
quality_gate_idle total_bytes_received 10/10 577.48KiB ≤ 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 480.04MiB ≤ 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 3 ≤ 6 bounds checks dashboard
quality_gate_logs memory_usage 10/10 181.55MiB ≤ 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.18MiB ≤ 292MiB bounds checks dashboard
quality_gate_metrics_logs cpu_usage 10/10 335.56 ≤ 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 396.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.86GiB ≤ 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".

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_logs baseline 10 Oom killed Debug Dashboard
quality_gate_logs 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 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 intake_connections: 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 missed_bytes: 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_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_logs, bounds check memory_usage: 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 missed_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.

@renovate renovate Bot changed the title Update module github.com/DataDog/dd-trace-go/v2 to v2.8.2 fix(deps): update module github.com/datadog/dd-trace-go/v2 to v2.8.2 Jun 24, 2026
@renovate renovate Bot changed the title fix(deps): update module github.com/datadog/dd-trace-go/v2 to v2.8.2 Update module github.com/DataDog/dd-trace-go/v2 to v2.8.2 Jun 25, 2026
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 medium review PR review might take time 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.

0 participants