Stuart McCulloch

Hi @Marcus-Rosti - we don't yet support trace propagation over akka-streams, you would need to use manual instrumentation to do that: https://docs.datadoghq.com/tracing/setup_overview/custom_instrumentation/java/#adding-spans

#2482 lets you name specific outbound requests to ignore (see discussion in https://github.com/DataDog/dd-trace-java/issues/2467#issuecomment-796703608) can be set as system property: ``` -Ddd.trace.grpc.ignored.outbound.methods=grpc.health.v1.Health/Check ``` or an environment variable: ``` DD_TRACE_GRPC_IGNORED_OUTBOUND_METHODS=grpc.health.v1.Health/Check ```

If you want to ignore inbound requests then that would require further work, but along the same lines as #2482

Summarizing the current status from the discussion at the end of #1823 > There's a limitation in AWS when it performs fanout from SNS to SQS where it doesn't propagate...

Thanks for the detailed analysis. This is not a comment on this specific PR, but I do think that this strategy of adding more and more ignores is not going...

Have you considered switching to Unix Domain Sockets? https://docs.datadoghq.com/developers/dogstatsd/unix_socket/?tab=kubernetes UDS has several benefits: * resistant to restarts (since it's not based on the agent IP which could change on restart)...

The only other workaround I know of is to have a cronjob that periodically cleans entries from the conntracks table, eg: ``` conntrack -D -p udp --dport 8125 ``` If...

Thanks @patrickhilgenstock - we're still working on full support for Java 17 in the Java tracer. For now you need to add this JDK option when running a JPMS modular...

Yes, this should work out-of-the-box if you attach the Java Tracer to both producing and consuming sides. The produce span will be attached to the consume span in the distributed...

The trace id and producing span id will be automatically added to every message if you have the Java Tracer attached to the JVM producing the message. Likewise if you...