From 7a796bdeedf5ce582a053fad3a57ceba938554f2 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Wed, 16 May 2018 13:09:43 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__features.html | 3 +-- single/spring-cloud-sleuth.html | 3 +-- spring-cloud-sleuth.xml | 3 +-- 3 files changed, 3 insertions(+), 6 deletions(-) diff --git a/multi/multi__features.html b/multi/multi__features.html index d11ea2dbd..0c16eb35e 100644 --- a/multi/multi__features.html +++ b/multi/multi__features.html @@ -8,8 +8,7 @@ When you want to wrap some operation in a Span and have it written to the logs o Spring Cloud Sleuth is loosely based on HTrace but is compatible with Zipkin (Dapper).
  • Sleuth records timing information to aid in latency analysis. By using sleuth, you can pinpoint causes of latency in your applications.

  • Sleuth is written to not log too much and to not cause your production application to crash. To that end, Sleuth:

    • Propagates structural data about your call graph in-band and the rest out-of-band.
    • Includes opinionated instrumentation of layers such as HTTP.
    • Includes a sampling policy to manage volume.
    • Can report to a Zipkin system for query and visualization.
  • Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).
  • Sleuth includes default logic to join a trace across HTTP or messaging boundaries. -For example, HTTP propagation works over Zipkin-compatible request headers. -This propagation logic is defined and customized through SpanInjector and SpanExtractor implementations.
  • Sleuth can propagate context (also known as baggage) between processes. +For example, HTTP propagation works over Zipkin-compatible request headers.
  • Sleuth can propagate context (also known as baggage) between processes. Consequently, if you set a baggage element on a Span, it is sent downstream to other processes over either HTTP or messaging.
  • Provides a way to create or continue spans and add tags and logs through annotations.

  • If spring-cloud-sleuth-zipkin is on the classpath, the app generates and collects Zipkin-compatible traces. By default, it sends them over HTTP to a Zipkin server on localhost (port 9411). You can configure the location of the service by setting spring.zipkin.baseUrl.

    • If you depend on spring-rabbit or spring-kafka, your app sends traces to a broker instead of HTTP. diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html index c0c66948b..479a46657 100644 --- a/single/spring-cloud-sleuth.html +++ b/single/spring-cloud-sleuth.html @@ -240,8 +240,7 @@ When you want to wrap some operation in a Span and have it written to the logs o Spring Cloud Sleuth is loosely based on HTrace but is compatible with Zipkin (Dapper).
    • Sleuth records timing information to aid in latency analysis. By using sleuth, you can pinpoint causes of latency in your applications.

    • Sleuth is written to not log too much and to not cause your production application to crash. To that end, Sleuth:

      • Propagates structural data about your call graph in-band and the rest out-of-band.
      • Includes opinionated instrumentation of layers such as HTTP.
      • Includes a sampling policy to manage volume.
      • Can report to a Zipkin system for query and visualization.
    • Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).
    • Sleuth includes default logic to join a trace across HTTP or messaging boundaries. -For example, HTTP propagation works over Zipkin-compatible request headers. -This propagation logic is defined and customized through SpanInjector and SpanExtractor implementations.
    • Sleuth can propagate context (also known as baggage) between processes. +For example, HTTP propagation works over Zipkin-compatible request headers.
    • Sleuth can propagate context (also known as baggage) between processes. Consequently, if you set a baggage element on a Span, it is sent downstream to other processes over either HTTP or messaging.
    • Provides a way to create or continue spans and add tags and logs through annotations.

    • If spring-cloud-sleuth-zipkin is on the classpath, the app generates and collects Zipkin-compatible traces. By default, it sends them over HTTP to a Zipkin server on localhost (port 9411). You can configure the location of the service by setting spring.zipkin.baseUrl.

      • If you depend on spring-rabbit or spring-kafka, your app sends traces to a broker instead of HTTP. diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml index 72e35440f..77a1cc5d0 100644 --- a/spring-cloud-sleuth.xml +++ b/spring-cloud-sleuth.xml @@ -644,8 +644,7 @@ To that end, Sleuth: Sleuth includes default logic to join a trace across HTTP or messaging boundaries. -For example, HTTP propagation works over Zipkin-compatible request headers. -This propagation logic is defined and customized through SpanInjector and SpanExtractor implementations. +For example, HTTP propagation works over Zipkin-compatible request headers. Sleuth can propagate context (also known as baggage) between processes.