false, Spring Cloud Sleuth does not instrument any of your custom Feign components.
However, all the default instrumentation is still there.In Spring Cloud Sleuth, we instrument async-related components so that the tracing information is passed between threads.
You can disable this behavior by setting the value of spring.sleuth.async.enabled to false.
If you annotate your method with @Async, we automatically create a new Span with the following characteristics:
- If the method is annotated with
@SpanName, the value of the annotation is the Span’s name. - If the method is not annotated with
@SpanName, the Span name is the annotated method name. - The span is tagged with the method’s class name and method name.
In Spring Cloud Sleuth, we instrument scheduled method execution so that the tracing information is passed between threads.
-You can disable this behavior by setting the value of spring.sleuth.scheduled.enabled to false.
If you annotate your method with @Scheduled, we automatically create a new span with the following characteristics:
- The span name is the annotated method name.
- The span is tagged with the method’s class name and method name.
If you want to skip span creation for some @Scheduled annotated classes, you can set the spring.sleuth.scheduled.skipPattern with a regular expression that matches the fully qualified name of the @Scheduled annotated class.
![[Tip]](images/tip.png) | Tip |
|---|---|
If you use |
We provide LazyTraceExecutor, TraceableExecutorService, and TraceableScheduledExecutorService. Those implementations create spans each time a new task is submitted, invoked, or scheduled.
The following example shows how to pass tracing information with TraceableExecutorService when working with CompletableFuture:
CompletableFuture<Long> completableFuture = CompletableFuture.supplyAsync(() -> {
+You can disable this behavior by setting the value of spring.sleuth.scheduled.enabled to false.If you annotate your method with @Scheduled, we automatically create a new span with the following characteristics:
- The span name is the annotated method name.
- The span is tagged with the method’s class name and method name.
If you want to skip span creation for some @Scheduled annotated classes, you can set the spring.sleuth.scheduled.skipPattern with a regular expression that matches the fully qualified name of the @Scheduled annotated class.
+If you use spring-cloud-sleuth-stream and spring-cloud-netflix-hystrix-stream together, a span is created for each Hystrix metrics and sent to Zipkin.
+This behavior may be annoying. That’s why, by default, spring.sleuth.scheduled.skipPattern=org.springframework.cloud.netflix.hystrix.stream.HystrixStreamTask.
We provide LazyTraceExecutor, TraceableExecutorService, and TraceableScheduledExecutorService. Those implementations create spans each time a new task is submitted, invoked, or scheduled.
The following example shows how to pass tracing information with TraceableExecutorService when working with CompletableFuture:
CompletableFuture<Long> completableFuture = CompletableFuture.supplyAsync(() -> {
// perform some logic
return 1_000_000L;
}, new TraceableExecutorService(beanFactory, executorService,
@@ -147,7 +147,7 @@ The following example shows how to set up such a custom Ex
}Features from this section can be disabled by setting the spring.sleuth.messaging.enabled property with value equal to false.
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
We instrument the To block this feature, set We instrument the Spring Kafka’s In Spring Cloud Sleuth, we instrument async-related components so that the tracing information is passed between threads.
You can disable this behavior by setting the value of If you annotate your method with
In Spring Cloud Sleuth, we instrument scheduled method execution so that the tracing information is passed between threads.
-You can disable this behavior by setting the value of If you annotate your method with
If you want to skip span creation for some
We provide The following example shows how to pass tracing information with CompletableFuture<Long> completableFuture = CompletableFuture.supplyAsync(() -> {
+You can disable this behavior by setting the value of We provide The following example shows how to pass tracing information with CompletableFuture<Long> completableFuture = CompletableFuture.supplyAsync(() -> {
// perform some logic
return 1_000_000L;
}, new TraceableExecutorService(beanFactory, executorService,
@@ -838,7 +838,7 @@ The following example shows how to set up such a custom Features from this section can be disabled by setting the Spring Cloud Sleuth integrates with Spring Integration.
It creates spans for publish and subscribe events.
To disable Spring Integration instrumentation, set You can provide the
|