Ex
It creates spans for publish and subscribe events.
To disable Spring Integration instrumentation, set spring.sleuth.integration.enabled to false.You can provide the spring.sleuth.integration.patterns pattern to explicitly provide the names of channels that you want to include for tracing.
By default, all channels but hystrixStreamOutput channel are included.
![[Important]](images/important.png) | Important |
|---|
When using the Executor to build a Spring Integration IntegrationFlow, you must use the untraced version of the Executor.
-Decorating the Spring Integration Executor Channel with TraceableExecutorService causes the spans to be improperly closed. |
We instrument the RabbitTemplate so that tracing headers get injected
+Decorating the Spring Integration Executor Channel with TraceableExecutorService causes the spans to be improperly closed.
If you want to customize the way tracing context is read from and written to message headers,
+it’s enough for you to register beans of types:
Propagation.Setter<MessageHeaderAccessor, String> - for writing headers to the messagePropagation.Getter<MessageHeaderAccessor, String> - for reading headers from the message
We instrument the RabbitTemplate so that tracing headers get injected
into the message.
To block this feature, set spring.sleuth.messaging.rabbit.enabled to false.
We instrument the Spring Kafka’s ProducerFactory and ConsumerFactory
so that tracing headers get injected into the created Spring Kafka’s
Producer and Consumer.
To block this feature, set spring.sleuth.messaging.kafka.enabled to false.
![[Note]](images/note.png) | Note |
|---|
We do not support context propagation via @KafkaListener annotation.
diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html
index 2ded8df3d..77158b98b 100644
--- a/single/spring-cloud-sleuth.html
+++ b/single/spring-cloud-sleuth.html
@@ -881,7 +881,8 @@ The following example shows how to set up such a custom Ex
It creates spans for publish and subscribe events.
To disable Spring Integration instrumentation, set spring.sleuth.integration.enabled to false. You can provide the spring.sleuth.integration.patterns pattern to explicitly provide the names of channels that you want to include for tracing.
By default, all channels but hystrixStreamOutput channel are included. | Important |
|---|
When using the Executor to build a Spring Integration IntegrationFlow, you must use the untraced version of the Executor.
-Decorating the Spring Integration Executor Channel with TraceableExecutorService causes the spans to be improperly closed. |
We instrument the RabbitTemplate so that tracing headers get injected
+Decorating the Spring Integration Executor Channel with TraceableExecutorService causes the spans to be improperly closed. |
If you want to customize the way tracing context is read from and written to message headers,
+it’s enough for you to register beans of types:
Propagation.Setter<MessageHeaderAccessor, String> - for writing headers to the messagePropagation.Getter<MessageHeaderAccessor, String> - for reading headers from the message
We instrument the RabbitTemplate so that tracing headers get injected
into the message.
To block this feature, set spring.sleuth.messaging.rabbit.enabled to false.
We instrument the Spring Kafka’s ProducerFactory and ConsumerFactory
so that tracing headers get injected into the created Spring Kafka’s
Producer and Consumer.
To block this feature, set spring.sleuth.messaging.kafka.enabled to false.
| Note |
|---|
We do not support context propagation via @KafkaListener annotation.
diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml
index 5a13842a6..90d5e5367 100644
--- a/spring-cloud-sleuth.xml
+++ b/spring-cloud-sleuth.xml
@@ -1921,6 +1921,16 @@ By default, all channels but hystrixStreamOutput channel are
When using the Executor to build a Spring Integration IntegrationFlow, you must use the untraced version of the Executor.
Decorating the Spring Integration Executor Channel with TraceableExecutorService causes the spans to be improperly closed.
+If you want to customize the way tracing context is read from and written to message headers,
+it’s enough for you to register beans of types:
+
+
+Propagation.Setter<MessageHeaderAccessor, String> - for writing headers to the message
+
+
+Propagation.Getter<MessageHeaderAccessor, String> - for reading headers from the message
+
+
|