Laplie Anderson

> Starting in version 0.74.0, the Java tracer automatically injects trace correlation identifiers into logs This part of the documentation is referring to the fact that up until 0.74.0, you...

@tyrcho You can manually create spans using the OpenTracing api by following the instructions [here](https://docs.datadoghq.com/tracing/setup_overview/custom_instrumentation/java#manually-creating-a-new-span). On that same page, there are instructions for creating a span with the `@Trace` annotation,...

The best way to accomplish this would be to use the OpenTracing `Tracer.inject()` and `Tracer.extract()`. **To inject on the producer side:** `tracer.inject(span.context(), Format.Builtin.HTTP_HEADERS, message);` **to extract on the consumer side:**...

@JianTray no problem. SQS support is definitely something we want to support natively and is already on our radar. I added #1823 to track. Closing this issue as resolved.

Converting to a draft while I investigate more tweaks

This is probably related to https://github.com/DataDog/dd-trace-java/pull/6651 . I believe the sonatype release process itself rebuilds the jar which leads to the difference. I'll investigate on Monday

@der-eismann That PR highlighted a much bigger issue. Different jobs are rebuilding the jar instead of reusing previously built artifacts. That includes more than just maven vs github release artifacts....

#7148 aligns the checksums.

@PerfectSlayer agreed. So much is removed from `.gitlab-ci.yml` that the diff is mostly useless. For the pruning workflow, I'm going to take a second look once most libraries are onboarded...

@Qard These pipeline runs on every push. For k8s injection, the image is tagged with the commit sha. For OCI images, the version is the version from the repo +...