Support W3C baggage propagation across various async instrumentation

[mcculls]

Motivation

Propagates the full context, including W3C baggage, over various async calls.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[datadog-datadog-prod-us1-2]

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 61.39% (+4.02%)

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

[mcculls]

@codex review

[Copilot]

Pull request overview

This PR updates async instrumentation and bootstrap concurrency helpers to propagate the full Datadog Context (including W3C baggage) across asynchronous boundaries, instead of propagating only the active span.

Changes:

• Switch multiple async instrumentations from activeSpan()-based capture to currentContext()/Context-based capture and continuation storage.
• Update bootstrap concurrency helpers (State, ConcurrentState, ExecutorInstrumentationUtils) to capture/propagate Context continuations (including contexts without spans when async propagation is enabled).
• Adjust bootstrap startup timing to install the legacy context manager earlier, and add Graal native-image build-time initialization for ContextProviders$ProvidedManager.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
dd-java-agent/instrumentation/spring/spring-rabbit-1.5/.../DeliveryInstrumentation.java	Capture Context instead of AgentSpan when attaching async State to deliveries.
dd-java-agent/instrumentation/scala/scala-promise/.../PromiseHelper.java	Activate/capture async state using Context continuations (for baggage propagation).
dd-java-agent/instrumentation/java/java-concurrent/.../CompletableFutureAdvice.java	Capture Context into ConcurrentState for CompletableFuture completions.
dd-java-agent/instrumentation/java/java-concurrent/.../ConsumerTaskInstrumentation.java	Capture Context into State for fork/join consumer tasks.
dd-java-agent/instrumentation/java/java-concurrent/.../JavaExecutorInstrumentation.java	Use Context in executor task wrapping/state setup decisions.
dd-java-agent/instrumentation/guava-10.0/.../ListenableFutureInstrumentation.java	Use Context in listener wrapping/state setup decisions for Guava futures.
dd-java-agent/instrumentation/graal/.../NativeImageGeneratorRunnerInstrumentation.java	Ensure ContextProviders$ProvidedManager is initialized at build time for native-image.
dd-java-agent/agent-bootstrap/.../java/concurrent/State.java	Store/capture ContextContinuation from Context instead of from span capture.
dd-java-agent/agent-bootstrap/.../java/concurrent/ExecutorInstrumentationUtils.java	Update attach/setup logic to be Context-driven and allow no-span contexts.
dd-java-agent/agent-bootstrap/.../java/concurrent/ConcurrentState.java	Capture and hold Context continuations for completable-future-style state.
dd-java-agent/agent-bootstrap/.../Agent.java	Install legacy context manager earlier in bootstrap startup sequence.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.89 s	[+0.2%; +1.5%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.91 s	13.07 s	[-2.0%; -0.5%] (maybe better)
startup:petclinic:appsec:Agent	16.89 s	16.84 s	[-0.7%; +1.4%] (no difference)
startup:petclinic:iast:Agent	16.83 s	16.95 s	[-1.5%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.69 s	16.78 s	[-1.8%; +0.7%] (no difference)
startup:petclinic:sca:Agent	16.93 s	16.80 s	[-0.2%; +1.8%] (no difference)
startup:petclinic:tracing:Agent	16.05 s	16.15 s	[-1.6%; +0.4%] (no difference)

Commit: 084bff08 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 59d706b7fa

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

[mcculls]

@codex review

[Copilot]

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 3 comments.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 084bff0804

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