From 874c67eb874927cfa6bdccd44fb37d64751cbcea Mon Sep 17 00:00:00 2001 From: buildmaster Date: Thu, 20 Dec 2018 12:50:14 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__introduction.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__introduction.html b/multi/multi__introduction.html index 86e7c15f8..a43f78a49 100644 --- a/multi/multi__introduction.html +++ b/multi/multi__introduction.html @@ -20,7 +20,7 @@ Span Id = D Client Sent

This note indicates that the current span has Trace Id set to X and Span Id set to D. Also, the Client Sent event took place.

The following image shows how parent-child relationships of spans look:

Parent child relationship

1.2 Purpose

The following sections refer to the example shown in the preceding image.

1.2.1 Distributed Tracing with Zipkin

This example has seven spans. If you go to traces in Zipkin, you can see this number in the second trace, as shown in the following image:

Traces

However, if you pick a particular trace, you can see four spans, as shown in the following image:

Traces Info propagation
[Note]Note

When you pick a particular trace, you see merged spans. -That means that, if there were two spans sent to Zipkin with Server Received and Server Sent or Client Received and Client Sent annotations, they are presented as a single span.

Why is there a difference between the seven and four spans in this case?

  • Two spans come from the http:/start span. It has the Server Received (sr) and Server Sent (ss) annotations.
  • Two spans come from the RPC call from service1 to service2 to the http:/foo endpoint. +That means that, if there were two spans sent to Zipkin with Server Received and Server Sent or Client Received and Client Sent annotations, they are presented as a single span.

Why is there a difference between the seven and four spans in this case?

  • One span comes from the http:/start span. It has the Server Received (sr) and Server Sent (ss) annotations.
  • Two spans come from the RPC call from service1 to service2 to the http:/foo endpoint. The Client Sent (cs) and Client Received (cr) events took place on the service1 side. Server Received (sr) and Server Sent (ss) events took place on the service2 side. These two spans form one logical span related to an RPC call.
  • Two spans come from the RPC call from service2 to service3 to the http:/bar endpoint. diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html index 7e3c0be59..a3eb4cb43 100644 --- a/single/spring-cloud-sleuth.html +++ b/single/spring-cloud-sleuth.html @@ -20,7 +20,7 @@ Span Id = D Client Sent

    This note indicates that the current span has Trace Id set to X and Span Id set to D. Also, the Client Sent event took place.

    The following image shows how parent-child relationships of spans look:

    Parent child relationship

1.2 Purpose

The following sections refer to the example shown in the preceding image.

1.2.1 Distributed Tracing with Zipkin

This example has seven spans. If you go to traces in Zipkin, you can see this number in the second trace, as shown in the following image:

Traces

However, if you pick a particular trace, you can see four spans, as shown in the following image:

Traces Info propagation
[Note]Note

When you pick a particular trace, you see merged spans. -That means that, if there were two spans sent to Zipkin with Server Received and Server Sent or Client Received and Client Sent annotations, they are presented as a single span.

Why is there a difference between the seven and four spans in this case?

  • Two spans come from the http:/start span. It has the Server Received (sr) and Server Sent (ss) annotations.
  • Two spans come from the RPC call from service1 to service2 to the http:/foo endpoint. +That means that, if there were two spans sent to Zipkin with Server Received and Server Sent or Client Received and Client Sent annotations, they are presented as a single span.

Why is there a difference between the seven and four spans in this case?

  • One span comes from the http:/start span. It has the Server Received (sr) and Server Sent (ss) annotations.
  • Two spans come from the RPC call from service1 to service2 to the http:/foo endpoint. The Client Sent (cs) and Client Received (cr) events took place on the service1 side. Server Received (sr) and Server Sent (ss) events took place on the service2 side. These two spans form one logical span related to an RPC call.
  • Two spans come from the RPC call from service2 to service3 to the http:/bar endpoint. diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml index f4362ebfd..baabf1231 100644 --- a/spring-cloud-sleuth.xml +++ b/spring-cloud-sleuth.xml @@ -114,7 +114,7 @@ That means that, if there were two spans sent to Zipkin with Server Received and Why is there a difference between the seven and four spans in this case? -Two spans come from the http:/start span. It has the Server Received (sr) and Server Sent (ss) annotations. +One span comes from the http:/start span. It has the Server Received (sr) and Server Sent (ss) annotations. Two spans come from the RPC call from service1 to service2 to the http:/foo endpoint.