Operation name/ Operation id missing for manual created threads about applicationinsights-java

[jeanbisutti]

@Charlie441324219 CompletableFuture is auto-instrumented but Thread is not.

You can do the following thing to propagate the context:

            io.opentelemetry.context.Context context = io.opentelemetry.context.Context.current();
			Thread thread = new Thread(new Runnable() {
			    @Override
			    public void run() {
					try (Scope scope = context.makeCurrent()) {
				telemetry.trackEvent(baseHeaders, null, membershipNbr, "AI_LOG_CHILDREN_THREAD_THREAD")).start();
					}
			    }
			});
			thread.start();

[Charlie441324219]

Hi @jeanbisutti ,

Thank you so much for your help, can you please provide more details about what condition context can auto propagate or what condition it cannot ?

[jeanbisutti]

de more details about what condition context can auto propagate or what condition it cannot ?

@Charlie441324219, The propagation context is automatically propagated between all the automatic instrumentations. So, the context is propagated to CompletableFuture and the HTTP request can be known.

Thread is not automatically instrumented. So, the context is not automatically propagated into the methods of Thread , and it is needed to programmatically propagate the context.

[Charlie441324219]

Hi @jeanbisutti , thank you for your reply, can you please provide more details about how to identify if a JAVA asynchronous technology is automatic instrumentations or not ?

[jeanbisutti]

See https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-add-modify?tabs=java

[trask]

hi @Charlie441324219, context is intentionally not propagated to manually created threads, see open-telemetry/opentelemetry-java-instrumentation#2527, other cases are generally handled

[Charlie441324219]

Thank you @jeanbisutti @trask ,