Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).
+Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, and Feign client).
Sleuth includes default logic to join a trace across HTTP or messaging boundaries. diff --git a/reference/html/appendix.html b/reference/html/appendix.html index bc20c3128..28edaffb9 100644 --- a/reference/html/appendix.html +++ b/reference/html/appendix.html @@ -350,7 +350,7 @@ Also, you can define your own properties.
spring.sleuth.scheduled.skip-pattern
org.springframework.cloud.netflix.hystrix.stream.HystrixStreamTask
Pattern for the fully qualified name of a class that should be skipped.
Pattern for URLs that should be skipped in tracing.
spring.sleuth.zuul.enabled
true
Enable span information propagation when using Zuul.
spring.zipkin.activemq.message-max-bytes
100000
Maximum number of bytes for a given message with spans sent to Zipkin over ActiveMQ.
Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).
+Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, and Feign client).
Sleuth includes default logic to join a trace across HTTP or messaging boundaries. diff --git a/reference/html/index.html b/reference/html/index.html index cccec3ea0..f87d57094 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -199,10 +199,9 @@ $(globalSwitch);
Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).
+Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, and Feign client).
Sleuth includes default logic to join a trace across HTTP or messaging boundaries. @@ -2155,10 +2154,6 @@ situation might be as follows:
AOP: If there was already a span created before an aspect was reached, you might not want to create a new span.
Hystrix: Executing a Hystrix command is most likely a logical part of the current processing. -It is in fact merely a technical implementation detail that you would not necessarily want to reflect in tracing as a separate being.
-spring.sleuth.schedu
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.
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.
We instrument the Zuul Ribbon integration by enriching the Ribbon requests with tracing information.
-To disable Zuul support, set the spring.sleuth.zuul.enabled property to false.
We set tracing property to Lettcue ClientResources instance to enable Brave tracing built in Lettuce .
To disable Redis support, set the spring.sleuth.redis.enabled property to false.
We instrument quartz jobs by adding Job/Trigger listeners to the Quartz Scheduler.
spring.sleuth.redis.enabled prope
For projects depending on Project Reactor such as Spring Cloud Gateway, we suggest turning the spring.sleuth.reactor.decorate-on-each option to false. That way an increased performance gain should be observed in comparison to the standard instrumentation mechanism. What this option does is it will wrap decorate onLast operator instead of onEach which will result in creation of far fewer objects. The downside of this is that when Project Reactor will change threads, the trace propagation will continue without issues, however anything relying on the ThreadLocal such as e.g. MDC entries can be buggy.
Provides an abstraction over common distributed tracing data models: traces, spans (forming a DAG), annotations, key-value annotations. Loosely based on HTrace, but Zipkin (Dapper) compatible.
Instruments common ingress and egress points from Spring applications (servlet filter, rest template, scheduled actions, message channels, zuul filters, feign client).
+Instruments common ingress and egress points from Spring applications (servlet filter, rest template, scheduled actions, message channels, feign client).
If spring-cloud-sleuth-zipkin is available then the app will generate and collect Zipkin-compatible traces via HTTP. By default it sends them to a Zipkin collector service on localhost (port 9411). Configure the location of the service using spring.zipkin.baseUrl.
Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).
+Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, and Feign client).
Sleuth includes default logic to join a trace across HTTP or messaging boundaries. @@ -2155,10 +2154,6 @@ situation might be as follows:
AOP: If there was already a span created before an aspect was reached, you might not want to create a new span.
Hystrix: Executing a Hystrix command is most likely a logical part of the current processing. -It is in fact merely a technical implementation detail that you would not necessarily want to reflect in tracing as a separate being.
-spring.sleuth.schedu
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.
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.
We instrument the Zuul Ribbon integration by enriching the Ribbon requests with tracing information.
-To disable Zuul support, set the spring.sleuth.zuul.enabled property to false.
We set tracing property to Lettcue ClientResources instance to enable Brave tracing built in Lettuce .
To disable Redis support, set the spring.sleuth.redis.enabled property to false.
We instrument quartz jobs by adding Job/Trigger listeners to the Quartz Scheduler.
spring.sleuth.redis.enabled prope
For projects depending on Project Reactor such as Spring Cloud Gateway, we suggest turning the spring.sleuth.reactor.decorate-on-each option to false. That way an increased performance gain should be observed in comparison to the standard instrumentation mechanism. What this option does is it will wrap decorate onLast operator instead of onEach which will result in creation of far fewer objects. The downside of this is that when Project Reactor will change threads, the trace propagation will continue without issues, however anything relying on the ThreadLocal such as e.g. MDC entries can be buggy.