Datadog context is not passed inside virtual threads.

Open

#9,984 opened on Nov 17, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: java, spring-boot
Domain: backend, observability

Research direction

The issue names no repository files or tests and provides no reproduction code. Start by reproducing the Spring Boot 3.5.7, Spring GraphQL, Spring HTTP Interfaces, Java 24.0.2, and virtual-thread setup, then compare it with the custom TaskDecorator. Done means Datadog context reaches GraphQL execution and outbound Spring HTTP Interface requests without manual propagation.

Written by the indexing model from the issue text.

Description

comp: context propagation type: bug report

Tracer Version(s)

1.55

Java Version(s)

24.0.2

JVM Vendor

Amazon Corretto

Bug Report

We have Spring Boot 3.5.7 with Spring GraphQL + using Spring HTTP Interfacases for requests. With enabled virtual threads there are no datadog trace id inside GraphQL execution context in in outbound requests made by Spring HTTP Interfaces.

To fix that we created custom code to manually pass datadog context inside virtual threads with TaskDecorator:

import datadog.trace.api.GlobalTracer;
import datadog.trace.api.Tracer;
import datadog.trace.context.TraceScope;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.core.task.TaskDecorator;

@Configuration
public class TracingConfiguration {

    @Bean
    public TaskDecorator datadogContextPropagatingTaskDecorator() {
        return runnable -> {
            Tracer tracer = GlobalTracer.get();
            TraceScope.Continuation continuation = tracer.captureActiveSpan();

            return () -> {
                if (continuation != null) {
                    try (TraceScope scope = continuation.activate()) {
                        runnable.run();
                    }
                } else {
                    runnable.run();
                }
            };
        };
    }
}

Expected Behavior

datadog agent automaticaly passes own context inside virtual threads and doesn't require manual context passing with custom code.

Reproduction Code

No response

Dominant language: Java
Stars: 737
Forks: 361
Avg merge: 3d 20h
Merged PRs (30d): 173

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Compatibility certification request for FJ-EAP 2.1.0 for Jakarta EE Platform 11 Open

certification

Difficulty 1/5 Under an hour Newbie friendliness 80/100

jakartaee/platform#1359 · Opened Sep 24, 2026
Python guide test runner copies stale Micronaut Test Resources state Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

micronaut-projects/micronaut-guides#1856 · Opened Sep 23, 2026
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Open

bug ecr

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

floci-io/floci#4264 · Opened Sep 23, 2026
Drop point numbers from GitHub milestones Open

Needs: Triage Type: Feature request

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

AntennaPod/AntennaPod#8794 · Opened Sep 23, 2026
[aw] Issue Classification Agent timed out Open

agentic-workflows

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

github/copilot-sdk#2760 · Opened Sep 23, 2026

More Java issues