[Draft; don't merge] v2.0.0-rc

[darccio]

What does this PR do?

This PR is a preview of the changes that will be merged into main for v2 release as github.com/DataDog/dd-trace-go/v2.

Motivation

These are the main motivations behind releasing a v2:

• Migrate from gopkg.in: this causes pain in enterprise customers.
• Long due refactor: moving away from interfaces in favor of concrete types in the API is a requirement to avoid situations where we had to hack a solution because adding functions caused breaking changes.
• Mitigate false-positive results from third party security scanners: due to our bloated go.mod pulling contrib’s dependencies. Also, remove deprecated dependencies’ contribs.
• Reduce library misuse: introduce better patterns, like using context to start spans to ensure trace propagation.
• Long backlog of proposals blocked waiting for a never-getting-planned v2.

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• Add an appropriate team label so this PR gets put in the right place for the release notes.

For Datadog employees:

• If this PR touches code that handles credentials of any kind, such as Datadog API keys, I've requested a review from @DataDog/security-design-and-guidance.
• This PR doesn't touch any of that.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-11 15:57:12

Comparing candidate commit 71d8ce2 in PR branch v2-dev with baseline commit e08fe35 in branch main.

Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥
Check Gitlab CI job log to find if any benchmark has crashed.

Scenarios present only in baseline:

• BenchmarkStartRequestSpan-24
• BenchmarkSampleWAFContext-24

Found 0 performance improvements and 8 performance regressions! Performance is the same for 47 metrics, 1 unstable metrics.

scenario:BenchmarkHttpServeTrace-24

• 🟥 allocations [+3; +3] or [+3.704%; +3.704%]
• 🟥 execution_time [+571.519ns; +696.881ns] or [+3.519%; +4.291%]

scenario:BenchmarkPartialFlushing/Enabled-24

• 🟥 execution_time [+5.488ms; +9.313ms] or [+2.006%; +3.404%]

scenario:BenchmarkSingleSpanRetention/no-rules-24

• 🟥 execution_time [+5.895µs; +8.771µs] or [+2.490%; +3.705%]

scenario:BenchmarkSingleSpanRetention/with-rules/match-all-24

• 🟥 execution_time [+10.143µs; +12.987µs] or [+4.247%; +5.438%]

scenario:BenchmarkSingleSpanRetention/with-rules/match-half-24

• 🟥 execution_time [+5.285µs; +8.235µs] or [+2.215%; +3.451%]

scenario:BenchmarkTracerAddSpans-24

• 🟥 allocated_mem [+56 bytes; +57 bytes] or [+2.462%; +2.486%]
• 🟥 execution_time [+131.270ns; +217.730ns] or [+3.386%; +5.617%]

[github-actions]

This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[datadog-datadog-prod-us1]

Datadog Report

Branch report: v2-dev
Commit report: 3d76ec0
Test service: dd-trace-go

❌ 25 Failed (1 Known Flaky), 2619 Passed, 67 Skipped, 1m 31.17s Total Time

❌ Failed Tests (25)

This report shows up to 5 failed tests.

• TestInjectTraceContextSizeLimit - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/eventbridge - Details

  Expand for error

   Failed
   
   === RUN   TestInjectTraceContextSizeLimit
   --- FAIL: TestInjectTraceContextSizeLimit (0.01s)
  

• TestInjectTraceContextSizeLimit/Do_not_inject_when_payload_is_too_large - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/eventbridge - Details

  Expand for error

   Failed
   
   === RUN   TestInjectTraceContextSizeLimit/Do_not_inject_when_payload_is_too_large
       --- FAIL: TestInjectTraceContextSizeLimit/Do_not_inject_when_payload_is_too_large (0.01s)
   panic: runtime error: invalid memory address or nil pointer dereference [recovered]
   	panic: runtime error: invalid memory address or nil pointer dereference
   [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x11e4699]
   
   goroutine 16 [running]:
   testing.tRunner.func1.2({0x12e0920, 0x1bef410})
   ...
  

• TestInjectTraceContext - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/sns - Details

  Expand for error

   Failed
   
   === RUN   TestInjectTraceContext
   --- FAIL: TestInjectTraceContext (0.05s)
  

• TestInjectTraceContext/No_injection_when_at_max_attributes - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/sns - Details

  Expand for error

   Failed
   
   === RUN   TestInjectTraceContext/No_injection_when_at_max_attributes
       --- FAIL: TestInjectTraceContext/No_injection_when_at_max_attributes (0.02s)
   panic: runtime error: invalid memory address or nil pointer dereference [recovered]
   	panic: runtime error: invalid memory address or nil pointer dereference
   [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x11e2cbf]
   
   goroutine 72 [running]:
   testing.tRunner.func1.2({0x12ddc20, 0x1bea410})
   ...
  

• TestInjectTraceContext - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/sqs - Details

  Expand for error

   Failed
   
   === RUN   TestInjectTraceContext
   --- FAIL: TestInjectTraceContext (0.05s)