If you’re using the Traverson library +}
If you’re using the Traverson library
it’s enough for you to inject a RestTemplate as a bean into your Traverson object. Since RestTemplate
is already intercepted, you will get full support of tracing in your client. Below you can find a pseudo code
of how to do that:
@Autowired RestTemplate restTemplate;
@@ -154,7 +154,7 @@ can see an example of how to set up such a custom Executor
executor.initialize();
return new LazyTraceExecutor(this.beanFactory, executor);
}
-}Spring Cloud Sleuth integrates with Spring Integration. It creates spans for publish and +}
Spring Cloud Sleuth integrates with Spring Integration. It creates spans for publish and
subscribe events. To disable Spring Integration instrumentation, set spring.sleuth.integration.enabled to false.
You can provide the spring.sleuth.integration.patterns pattern to explicitly
provide the names of channels that you want to include for tracing. By default all channels
are included.
![[Important]](images/important.png) | Important |
|---|---|
When using the Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud. Spring Cloud Sleuth borrows Dapper’s terminology. Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an + Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud. Spring Cloud Sleuth borrows Dapper’s terminology. Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address). Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -34,7 +34,7 @@ service2.log:2016-02-26 11:15:47.924 INFO [service2,2485ec27856c56f4,9aa10ee6fb service4.log:2016-02-26 11:15:48.134 INFO [service4,2485ec27856c56f4,1b1845262ffba49d,true] 68061 --- [nio-8084-exec-1] i.s.c.sleuth.docs.service4.Application : Hello from service4 service2.log:2016-02-26 11:15:48.156 INFO [service2,2485ec27856c56f4,9aa10ee6fbde75fa,true] 68059 --- [nio-8082-exec-1] i.s.c.sleuth.docs.service2.Application : Got response from service4 [Hello from service4] service1.log:2016-02-26 11:15:48.182 INFO [service1,2485ec27856c56f4,2485ec27856c56f4,true] 68058 --- [nio-8081-exec-1] i.s.c.sleuth.docs.service1.Application : Got response from service2 [Hello from service2, response from service3 [Hello from service3] and from service4 [Hello from service4]] If you’re using a log aggregating tool like Kibana, -Splunk etc. you can order the events that took place. An example of +Splunk etc. you can order the events that took place. An example of Kibana would look like this:  If you want to use Logstash here is the Grok pattern for Logstash: filter {
# pattern matching logback pattern
grok {
diff --git a/1.3.x/multi/multi__metrics.html b/1.3.x/multi/multi__metrics.html
index a3ae473fa..911b23b25 100644
--- a/1.3.x/multi/multi__metrics.html
+++ b/1.3.x/multi/multi__metrics.html
@@ -1,7 +1,7 @@
|
By default if you add spring-cloud-starter-zipkin as a dependency to your project,
when the span is closed, it will be sent to Zipkin over HTTP. The communication
is asynchronous. You can configure the URL by setting the spring.zipkin.baseUrl
-property as follows:
spring.zipkin.baseUrl: http://192.168.99.100:9411/
If you want to find Zipkin via service discovery it’s enough to pass the +property as follows:
spring.zipkin.baseUrl: https://192.168.99.100:9411/
If you want to find Zipkin via service discovery it’s enough to pass the
Zipkin’s service id inside the URL. If you want to disable this feature
just set spring.zipkin.discoveryClientEnabled to false.
Example for `zipkinserver service id:
spring.zipkin.baseUrl: http://zipkinserver/When this Discovery Client feature is enabled, Sleuth uses diff --git a/1.3.x/multi/multi__span_data_as_messages.html b/1.3.x/multi/multi__span_data_as_messages.html index 6fdedfa0b..f41490a46 100644 --- a/1.3.x/multi/multi__span_data_as_messages.html +++ b/1.3.x/multi/multi__span_data_as_messages.html @@ -1,7 +1,7 @@
You can accumulate and send span data over
-Spring Cloud Stream by
+Spring Cloud Stream by
including the spring-cloud-sleuth-stream jar as a dependency, and
adding a Channel Binder implementation
(e.g. spring-cloud-starter-stream-rabbit for RabbitMQ or
diff --git a/1.3.x/single/spring-cloud-sleuth.html b/1.3.x/single/spring-cloud-sleuth.html
index 9b53c6211..1131a2bb4 100644
--- a/1.3.x/single/spring-cloud-sleuth.html
+++ b/1.3.x/single/spring-cloud-sleuth.html
@@ -1,6 +1,6 @@
Table of Contents
- 1. Introduction
- 2. Additional resources
- 3. Features
- 4. Sampling
- 5. Instrumentation
- 6. Span lifecycle
- 7. Naming spans
- 8. Managing spans with annotations
- 9. Customizations
- 10. Sending spans to Zipkin
- 11. Span Data as Messages
- 12. Metrics
- 13. Integrations
- 14. Running examples
Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.
Spring Cloud Sleuth borrows Dapper’s terminology.
Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +
Table of Contents
- 1. Introduction
- 2. Additional resources
- 3. Features
- 4. Sampling
- 5. Instrumentation
- 6. Span lifecycle
- 7. Naming spans
- 8. Managing spans with annotations
- 9. Customizations
- 10. Sending spans to Zipkin
- 11. Span Data as Messages
- 12. Metrics
- 13. Integrations
- 14. Running examples
Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.
Spring Cloud Sleuth borrows Dapper’s terminology.
Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).
Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -34,7 +34,7 @@ service2.log:2016-02-26 11:15:47.924 INFO [service2,2485ec27856c56f4,9aa10ee6fb service4.log:2016-02-26 11:15:48.134 INFO [service4,2485ec27856c56f4,1b1845262ffba49d,true] 68061 --- [nio-8084-exec-1] i.s.c.sleuth.docs.service4.Application : Hello from service4 service2.log:2016-02-26 11:15:48.156 INFO [service2,2485ec27856c56f4,9aa10ee6fbde75fa,true] 68059 --- [nio-8082-exec-1] i.s.c.sleuth.docs.service2.Application : Got response from service4 [Hello from service4] service1.log:2016-02-26 11:15:48.182 INFO [service1,2485ec27856c56f4,2485ec27856c56f4,true] 68058 --- [nio-8081-exec-1] i.s.c.sleuth.docs.service1.Application : Got response from service2 [Hello from service2, response from service3 [Hello from service3] and from service4 [Hello from service4]]
If you’re using a log aggregating tool like Kibana, -Splunk etc. you can order the events that took place. An example of +Splunk etc. you can order the events that took place. An example of Kibana would look like this:
If you want to use Logstash here is the Grok pattern for Logstash:
filter {
# pattern matching logback pattern
grok {
@@ -576,7 +576,7 @@ By default it sends them via HTTP to a Zipkin server on localhost (port 9411). I
on spring-rabbit or spring-kafka your app will send traces to a broker instead of http.By default if you add spring-cloud-starter-zipkin as a dependency to your project,
when the span is closed, it will be sent to Zipkin over HTTP. The communication
is asynchronous. You can configure the URL by setting the spring.zipkin.baseUrl
-property as follows:
spring.zipkin.baseUrl: http://192.168.99.100:9411/
If you want to find Zipkin via service discovery it’s enough to pass the +property as follows:
spring.zipkin.baseUrl: https://192.168.99.100:9411/
If you want to find Zipkin via service discovery it’s enough to pass the
Zipkin’s service id inside the URL. If you want to disable this feature
just set spring.zipkin.discoveryClientEnabled to false.
Example for `zipkinserver service id:
spring.zipkin.baseUrl: http://zipkinserver/When this Discovery Client feature is enabled, Sleuth uses
@@ -604,7 +604,7 @@ object, you will have to create a bean of zipkin2.reporter
zipkinRestTemplateCustomizer.customize(restTemplate);
return myCustomSender(zipkin, restTemplate);
}
You can accumulate and send span data over
-Spring Cloud Stream by
+Spring Cloud Stream by
including the spring-cloud-sleuth-stream jar as a dependency, and
adding a Channel Binder implementation
(e.g. spring-cloud-starter-stream-rabbit for RabbitMQ or
@@ -673,7 +673,7 @@ with name equal to StreamSpanReporter.POLLER. Here
return poller;
}
}
Currently Spring Cloud Sleuth registers very simple metrics related to spans. -It’s using the Spring Boot’s metrics support +It’s using the Spring Boot’s metrics support to calculate the number of accepted and dropped spans. Each time a span gets sent to Zipkin the number of accepted spans will increase. If there’s an error then the number of dropped spans will get increased.
If you’re wrapping your logic in Runnable or Callable it’s enough to wrap those classes in their Sleuth representative.
Example for Runnable:
Runnable runnable = new Runnable() {
@@ -789,7 +789,7 @@ can see an example of how to set up such a custom AsyncRes
//CUSTOMIZE HERE
return factory;
}
-}If you’re using the Traverson library +}
If you’re using the Traverson library
it’s enough for you to inject a RestTemplate as a bean into your Traverson object. Since RestTemplate
is already intercepted, you will get full support of tracing in your client. Below you can find a pseudo code
of how to do that:
@Autowired RestTemplate restTemplate;
@@ -830,7 +830,7 @@ can see an example of how to set up such a custom Executor
executor.initialize();
return new LazyTraceExecutor(this.beanFactory, executor);
}
-}Spring Cloud Sleuth integrates with Spring Integration. It creates spans for publish and +}
Spring Cloud Sleuth integrates with Spring Integration. It creates spans for publish and
subscribe events. To disable Spring Integration instrumentation, set spring.sleuth.integration.enabled to false.
You can provide the spring.sleuth.integration.patterns pattern to explicitly
provide the names of channels that you want to include for tracing. By default all channels
are included.
| Important |
|---|---|
When using the You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links: You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links: |