anchor.diff:      compile("io.zipkin.brave:brave-instrumentation-grpc")
   ```
   
  -==== Server Instrumentation
  +===== Server Instrumentation
   
   Spring Cloud Sleuth leverages grpc-spring-boot-starter to register Brave's gRPC server interceptor with all services annotated with `@GRpcService`. 
   
  -==== Client Instrumentation
  +===== Client Instrumentation
   
   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.
   
  
positive.code: 
  Sleuth creates a `TracingManagedChannelBuilderCustomizer` which inject Brave's client interceptor into the `SpringAwareManagedChannelBuilder`.
  
  
  === Asynchronous Communication
  
  
negative.code: 
  Spring Cloud Sleuth provides instrumentation for https://grpc.io/[gRPC] through `TraceGrpcAutoConfiguration`. You can disable it entirely by setting `spring.sleuth.grpc.enabled` to `false`.
  
  ==== Variant 1
  
  ===== Dependencies
  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: 
  