SpringCloud/spring-cloud-sleuth
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Configure Reactor instrumentation to wrap onLastOperator or onEachOperator

Browse Source 
with this feature we would allow user to pick whether they instrument on each or on last operator.

fixes gh-1478
This commit is contained in:
Marcin Grzejszczak
2019-10-30 13:09:30 +01:00
parent 759ac87481
commit cd2e2c2d49
6 changed files with 191 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/main/asciidoc/spring-cloud-sleuth.adoc
View File

@@ -1413,6 +1413,10 @@ IMPORTANT: We don't support baggage propagation for JMS
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`.
=== Project Reactor
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.
== Running examples
You can see the running examples deployed in the https://run.pivotal.io/[Pivotal Web Services].