4.0.0

Type	Description	Link
Break	Scheduled executor recurring tasks are always given new trace IDs Previously we had no good options for scheduled executors: Either create a new traceId for every taskd regardless of whether it was submitted to execute(runnable) or scheduleWithFixedDelay which mean very different things. Recurring tasks are most frequently scheduled on application startup and continue to execute at a cadence until the service is halted. In these cases we used to produce large traces bounded by the runtime of the application, making the traceId of an error thrown in this context unhelpful for debugging. In worse cases, lazily scheduled tasks are created with the traceId of a request that happened to cause lazy initialization, resulting in tracing state that incorrectly blames to a particular user request. While there are cases that we may want to preserve a single traceId across a scheduled task, they are sparse and complex. In these cases it's reasonable to expect developers to wrap tasks before scheduling them with an executor to acknowledge the desired behavior, and make it clear to others who read the code.	#362

3.4.1

Type	Description	Link
Fix	Replace Trace headers instead of appending them.	#350

3.4.0

Type	Description	Link
Improvement	Tracers.wrapListenableFuture utility to wrap ListenableFutures with detached spans	#328

3.3.0

Type	Description	Link
Improvement	Tracing aware executors wrap Runnables and Callables more cleanly	#310

3.2.0

Type	Description	Link
Improvement	Implement asynchronous operation tracing using DetachedSpan.	#124
Fix	tracing-test-utils: Fix ordering bugs in SpanAnalyser, and correctly serde span type.	#250

3.2.0-rc2

Type	Description	Link
Improvement	Implement asynchronous operation tracing using DetachedSpan.	#124

3.2.0-rc1

Type	Description	Link
Feature	Create new tracing-test-utils package which allows you to render traces and snapshot test them.	#235

3.1.0

Type	Description	Link
Improvement	Add originating span id to requests in order to enable request log tracing	#206

3.0.0

Type	Description	Link
Break	Removed jackson-databind and jackson-annotations from tracing-api.	#209

2.16.0

This release introduces new Tracer.fastStartSpan alternative to startSpan for invocations which do not need the returned OpenSpan object. Error prone will helpfully validate that startSpan is only used when the return value is checked.

• [improvement] use of factory method to avoid OpenSpan.Builder allocations (#167)
• [improvement] Tracer spans are inexpensive for unsampled operations (#180)