From 14ff6644536ee09b8f009464b7a15169d8e71460 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Tue, 14 Aug 2018 14:55:17 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__features.html | 2 +- single/spring-cloud-sleuth.html | 2 +- spring-cloud-sleuth.xml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/multi/multi__features.html b/multi/multi__features.html index 6c2740f7c..0965f3d2d 100644 --- a/multi/multi__features.html +++ b/multi/multi__features.html @@ -71,7 +71,7 @@ The former is simpler to understand and test and does not tempt users with span void userCode() { span.annotate("tx.started"); ... -}

3.1.5 RPC tracing

[Tip]Tip

Check for instrumentation written here and Zipkin’s list before rolling your own RPC instrumentation.

RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation.

The following example shows how to add a client span:

@Autowired Tracer tracer;
+}

3.1.5 RPC tracing

[Tip]Tip

Check for instrumentation written here and Zipkin’s list before rolling your own RPC instrumentation.

RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation.

The following example shows how to add a client span:

@Autowired Tracer tracer;
 
 // before you send a request, add metadata that describes the operation
 span = tracer.newTrace().name("get").type(CLIENT);
diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html
index 0d474837c..2d9361049 100644
--- a/single/spring-cloud-sleuth.html
+++ b/single/spring-cloud-sleuth.html
@@ -314,7 +314,7 @@ The former is simpler to understand and test and does not tempt users with span
 void userCode() {
   span.annotate("tx.started");
   ...
-}

3.1.5 RPC tracing

[Tip]Tip

Check for instrumentation written here and Zipkin’s list before rolling your own RPC instrumentation.

RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation.

The following example shows how to add a client span:

@Autowired Tracer tracer;
+}

3.1.5 RPC tracing

[Tip]Tip

Check for instrumentation written here and Zipkin’s list before rolling your own RPC instrumentation.

RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation.

The following example shows how to add a client span:

@Autowired Tracer tracer;
 
 // before you send a request, add metadata that describes the operation
 span = tracer.newTrace().name("get").type(CLIENT);
diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml
index 28ea4e452..9e9151a18 100644
--- a/spring-cloud-sleuth.xml
+++ b/spring-cloud-sleuth.xml
@@ -810,7 +810,7 @@ void userCode() {
 

 RPC tracing
 
-Check for instrumentation written here and Zipkin’s list before rolling your own RPC instrumentation.
+Check for instrumentation written here and Zipkin’s list before rolling your own RPC instrumentation.
 
 RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation.
 The following example shows how to add a client span: