From bed01f27797ebbbcba3ab8eb821e7dad569c89bc Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Mon, 23 May 2016 11:03:39 +0200 Subject: [PATCH] Revert "Updated docs for Kafka binder configuration" This reverts commit 47bb27db12bc17731dd71a58878f00c6653efd9e. --- .../main/asciidoc/spring-cloud-sleuth.adoc | 24 ------------------- 1 file changed, 24 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-sleuth.adoc b/docs/src/main/asciidoc/spring-cloud-sleuth.adoc index 3f5ddd8d3..dd344dea5 100644 --- a/docs/src/main/asciidoc/spring-cloud-sleuth.adoc +++ b/docs/src/main/asciidoc/spring-cloud-sleuth.adoc @@ -351,30 +351,6 @@ NOTE: the sample consumer application above explicitly excludes but this is optional (you might actually want to trace requests into the consumer app). -=== Spring Cloud Stream Kafka binder configuration - -In order to integrate header propagation with Spring Cloud Stream Kafka as a binder you have to provide in your -configuration file the following headers: - -[source,yaml] ----- -spring: - cloud: - stream: - kafka: - binder: - headers: - - X-B3-TraceId - - X-B3-SpanId - - X-B3-Sampled - - X-B3-ParentSpanId - - X-Span-Name - - X-Process-Id ----- - -TIP: If you have a custom `SpanExtractor` where you pass custom headers you need to provide those too in the -configuration file. - == Metrics Currently Spring Cloud Sleuth registers very simple metrics related to spans.