Stuart McCulloch

yes, that appears to be the latest release of OpenJ9 - I've asked our profiler team if they've seen this before meanwhile I'd recommend you open a ticket with the...

If you set the following system property on both the producing and consuming sides: ``` -Ddd.kafka.legacy.tracing.enabled=false ``` then the consume span will now have the local servicename and a new...

Hi Gerrick, The trace and span ids recorded in the `ConsumerRecord` are only extracted and used as the context at the point where we create the `kafka.consume` span - before...

thanks for the example - I see that Alpakka-kafka builds on akka-streams which we don't yet support (we also don't have support for web-socket propagation) you should be able to...

I notice this only runs the matcher against loaded classes - all the byte-buddy matchers are designed so they can run against bytecode, ie. the class resource, without having to...

Hi @dan-lind if you don't want tracer logging in your application logs then you can route it to a separate file with `-Ddatadog.slf4j.simpleLogger.logFile=path/to/tracer.log` (note: other [SimpleLogger](https://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html) settings can be used...

Yes I agree, I'll pass on your feedback

Hi @unlucku - there are only a handful of properties that have no effect in the external DD_TRACE_CONFIG file. Those properties are the top-level switches to enable the profiler, tracer,...

Hi @ihangji - which version of the Java tracer are you using? Based on the stack trace this looks like a [known issue](https://github.com/DataDog/dd-trace-java/releases/tag/v0.76.0) where metrics aggregation was incorrectly enabled in...

Thanks @tylerbenson - https://github.com/DataDog/dd-trace-java/pull/3687 should fix the logging