From 326a37bf5ac7caa0487792cf5cd8676154302111 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Thu, 10 Nov 2016 15:49:41 +0100 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud-sleuth.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/spring-cloud-sleuth.html b/spring-cloud-sleuth.html index 96c2d9404..055b219bc 100644 --- a/spring-cloud-sleuth.html +++ b/spring-cloud-sleuth.html @@ -434,11 +434,11 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
  • Log correlation @@ -908,8 +908,9 @@ If you’re using a custom logback-spring.xml then you have to -
    -
    Propagating Span Context
    +
    +
    +

    Propagating Span Context

    The span context is the state that must get propagated to any child Spans across process boundaries. Part of the Span Context is the Baggage. The trace and span IDs are a required part of the span context. @@ -935,7 +936,7 @@ to exceeding transport-level message or header capacity.

    -

    Example of setting span:

    +

    Example of setting baggage on a span:

    @@ -943,8 +944,8 @@ to exceeding transport-level message or header capacity. initialSpan.setBaggageItem("foo", "bar");
    -
    -
    Baggage vs. Span Tags
    +
    +
    Baggage vs. Span Tags

    Baggage travels with the trace (i.e. every child span contains the baggage of its parent). Zipkin has no knowledge of baggage and will not even receive that information.

    @@ -970,7 +971,6 @@ tracer.addTag(baggageKey, baggageValue);
    -

    Adding to the project