In kafka events, the traceId and spanId are not written in the logs

[oooximionnn]

In kafka events, the traceId and spanId are not written in the logs

[jonatan-ivanov]

You might be in the wrong repo. :)
Micrometer Tracing is for Distributed Tracing but you might want to open this issue for Spring Kafka instead.

Also, please consider these:

• Why is the KafkaTemplateObservationConvention relevant? Can you repro the issue without it?
• How about the custom AsyncConfig/ThreadPoolTaskScheduler and ContextExecutorService usage?
• logging.pattern.console
• You might want to check what properties under management.tracing.propagation doing (type overrides the other two)

I'm not sure this is because of your custom async config or creating a scope is missing somewhere in the instrumentation.

/cc @artembilan

[oooximionnn]

I did as you said: Why is the KafkaTemplateObservationConvention relevant? Can you repro the issue without it?
But it didn't help.

We also used this link: https://github.com/micrometer-metrics/micrometer-samples/blob/main/kafka-producer/src/main/java/com/example/micrometer/ManualConfiguration.java
It didn't help.

[oooximionnn]

The problem is related to the transition to spring boot 3. On Spring boot 2, the Sleuth library was used for tracing and kafka event tracing was present. But when we started using examples and instructions from micrometer, trace id did not appear, it only appeared in kafka headers

[artembilan]

The kafkaTemplate.setObservationEnabled(true); adds an observation around a producer record send operation.
It has nothing to do with whatever is there afterwards with returned Future.
I believe that .thenAccept(result -> { might be performed on a different thread which is out of @Async control.