Bump github.com/DataDog/dd-trace-go/v2 from 2.7.1 to 2.8.1 in /projects/coredns/coredns/1-35

[dependabot]

Bumps github.com/DataDog/dd-trace-go/v2 from 2.7.1 to 2.8.1.

Release notes

Sourced from github.com/DataDog/dd-trace-go/v2's releases.

v2.8.1

Application Performance Monitoring (APM)

• Revert "fix(ddtrace/tracer): cache trace ID hex encoding (#4481)" by @​darccio
• fix(tracer): enforce baggage item and byte limits on extraction by @​mtoffl01 in #4720
• fix(tracer): drop dd= list-entries over 256 bytes from incoming tracestate by @​mtoffl01 in #4721

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

v2.8.0

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)

• feat: collect service override source by @​raphaelgavache in DataDog/dd-trace-go#4500
• feat: support service source for 19 integrations by @​raphaelgavache in DataDog/dd-trace-go#4526
• feat: support service source for 13integrations by @​raphaelgavache in DataDog/dd-trace-go#4534
• feat: add service source on 10 integrations by @​raphaelgavache in DataDog/dd-trace-go#4540
• feat: force usage of ServiceWithSource in contrib by @​raphaelgavache in DataDog/dd-trace-go#4549
• fix(eventbridge): update max payload size to 1m by @​Dogbu-cyber in DataDog/dd-trace-go#4458
• feat(telemetry): add stable session identifier headers by @​khanayan123 in DataDog/dd-trace-go#4574
• feat: collect service source in client stats by @​raphaelgavache in DataDog/dd-trace-go#4519
• feat: OTel process context v2 (otlp proto) by @​nsavoire in DataDog/dd-trace-go#4478
• fix: join redis and valkey pipeline commands with newlines for correct agent obfuscation by @​rarguelloF in DataDog/dd-trace-go#4593

... (truncated)

Commits

• 2b2b2c2 chore: make fix-modules && make generate
• 21438ed internal/version: v2.8.1
• 0bc11f3 internal/orchestrion/_integration: v2.8.1-rc.2
• f17a712 orchestrion/all: v2.8.1-rc.2
• 1b8d8e5 internal/traceprof/traceproftest: v2.8.1-rc.2
• 7b30b1f contrib/aws/datadog-lambda-go/test/integration_tests/error: v2.8.1-rc.2
• 96cc2a4 contrib/aws/datadog-lambda-go/test/integration_tests/hello: v2.8.1-rc.2
• f3013b5 instrumentation/internal/validationtest: v2.8.1-rc.2
• c9f9843 contrib/labstack/echo.v4: v2.8.1-rc.2
• e07b30b contrib/valyala/fasthttp: v2.8.1-rc.2
• Additional commits viewable in compare view

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign charles-large for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[eks-distro-bot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a aws member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.