From 9b0cc329c4fc4a883ea3eb63dbf9360c8adfe07c Mon Sep 17 00:00:00 2001 From: buildmaster Date: Wed, 1 Aug 2018 14:48:34 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__integrations.html | 3 ++- single/spring-cloud-sleuth.html | 3 ++- spring-cloud-sleuth.xml | 10 ++++++++++ 3 files changed, 14 insertions(+), 2 deletions(-) diff --git a/multi/multi__integrations.html b/multi/multi__integrations.html index 7307baabb..75ec9aa71 100644 --- a/multi/multi__integrations.html +++ b/multi/multi__integrations.html @@ -150,7 +150,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]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.

15.9.2 Spring RabbitMq

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 message
  • Propagation.Getter<MessageHeaderAccessor, String> - for reading headers from the message

15.9.2 Spring RabbitMq

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.

15.9.3 Spring Kafka

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]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]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.

15.9.2 Spring RabbitMq

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 message
  • Propagation.Getter<MessageHeaderAccessor, String> - for reading headers from the message

15.9.2 Spring RabbitMq

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.

15.9.3 Spring Kafka

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]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 + +

Spring RabbitMq