Part of Feign instrumentation is done through a FeignBeanPostProcessor.
You can disable it by setting spring.sleuth.feign.processor.enabled to false.
If you set it to false, Spring Cloud Sleuth does not instrument any of your custom Feign components.
-However, all the default instrumentation is still there.
Spring Cloud Sleuth provides instrumentation for gRPC through TraceGrpcAutoConfiguration. You can disable it entirely by setting spring.sleuth.grpc.enabled to false.
![[Important]](images/important.png) | Important |
|---|---|
The gRPC integration relies on two external libraries to instrument clients and servers and both of those libraries must be on the class path to enable the instrumentation. |
Maven:
<dependency> +However, all the default instrumentation is still there.
Spring Cloud Sleuth provides instrumentation for gRPC through TraceGrpcAutoConfiguration. You can disable it entirely by setting spring.sleuth.grpc.enabled to false.
| Important |
|---|---|
The gRPC integration relies on two external libraries to instrument clients and servers and both of those libraries must be on the class path to enable the instrumentation. |
Maven:
<dependency> <groupId>io.github.lognet</groupId> <artifactId>grpc-spring-boot-starter</artifactId> </dependency> @@ -132,7 +132,7 @@ However, all the default instrumentation is still there.
Spring Cloud Sleuth leverages grpc-spring-boot-starter to register Brave’s gRPC server interceptor with all services annotated with @GRpcService.
gRPC clients leverage a ManagedChannelBuilder to construct a ManagedChannel used to communicate to the gRPC server. The native ManagedChannelBuilder provides static methods as entry points for construction of ManagedChannel instances, however, this mechanism is outside the influence of the Spring application context.
| Important |
|---|---|
Spring Cloud Sleuth provides a |
Sleuth creates a TracingManagedChannelBuilderCustomizer which inject Brave’s client interceptor into the SpringAwareManagedChannelBuilder.
In Spring Cloud Sleuth, we instrument async-related components so that the tracing information is passed between threads. + compile("io.zipkin.brave:brave-instrumentation-grpc")
Spring Cloud Sleuth leverages grpc-spring-boot-starter to register Brave’s gRPC server interceptor with all services annotated with @GRpcService.
gRPC clients leverage a ManagedChannelBuilder to construct a ManagedChannel used to communicate to the gRPC server. The native ManagedChannelBuilder provides static methods as entry points for construction of ManagedChannel instances, however, this mechanism is outside the influence of the Spring application context.
| Important |
|---|---|
Spring Cloud Sleuth provides a |
Sleuth creates a TracingManagedChannelBuilderCustomizer which inject Brave’s client interceptor into the SpringAwareManagedChannelBuilder.
Grpc Spring Boot Starter automatically detects the presence of Spring Cloud Sleuth and brave’s instrumentation for gRPC and registers the necessary client and/or server tooling.
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.
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.
diff --git a/multi/multi_spring-cloud-sleuth.html b/multi/multi_spring-cloud-sleuth.html
index a216c00be..55162b4a2 100644
--- a/multi/multi_spring-cloud-sleuth.html
+++ b/multi/multi_spring-cloud-sleuth.html
@@ -1,3 +1,3 @@
Table of Contents
- 1. Introduction
- 2. Additional Resources
- 3. Features
- 4. Sampling
- 5. Propagation
- 6. Current Tracing Component
- 7. Current Span
- 8. Instrumentation
- 9. Span lifecycle
- 10. Naming spans
- 11. Managing Spans with Annotations
- 12. Customizations
- 13. Sending Spans to Zipkin
- 14. Zipkin Stream Span Consumer
- 15. Integrations
- 16. Running examples
Table of Contents
- 1. Introduction
- 2. Additional Resources
- 3. Features
- 4. Sampling
- 5. Propagation
- 6. Current Tracing Component
- 7. Current Span
- 8. Instrumentation
- 9. Span lifecycle
- 10. Naming spans
- 11. Managing Spans with Annotations
- 12. Customizations
- 13. Sending Spans to Zipkin
- 14. Zipkin Stream Span Consumer
- 15. Integrations
- 16. Running examples